diff doc/customizing.txt @ 5067:e424987d294a

Add support for an integer type to join the existing number type. Commit patch supplied for issue2550886. This can be used for properties used for ordering, counts etc. where a decimal point isn't needed. Developed by Anthony (antmail). Doc updates written by John Rouillard.
author John Rouillard <rouilj@ieee.org>
date Sun, 05 Jun 2016 00:17:26 -0400
parents 46da0db55545
children f74300d1494e
line wrap: on
line diff
--- a/doc/customizing.txt	Tue May 31 09:16:09 2016 +0200
+++ b/doc/customizing.txt	Sun Jun 05 00:17:26 2016 -0400
@@ -655,6 +655,7 @@
   class.
 * Date properties store date-and-time stamps. Their values are Timestamp
   objects.
+* Integer properties store integer values. (Number can store real/float values.)
 * Number properties store numeric values.
 * Boolean properties store on/off, yes/no, true/false values.
 * A Link property refers to a single other item selected from a
@@ -814,8 +815,9 @@
 When we sort items in the hyperdb, we use one of a number of methods,
 depending on the properties being sorted on:
 
-1. If it's a String, Number, Date or Interval property, we just sort the
-   scalar value of the property. Strings are sorted case-sensitively.
+1. If it's a String, Integer, Number, Date or Interval property, we
+   just sort the scalar value of the property. Strings are sorted
+   case-sensitively.
 2. If it's a Link property, we sort by either the linked item's "order"
    property (if it has one) or the linked item's "id".
 3. Mulitlinks sort similar to #2, but we start with the first Multilink
@@ -1660,7 +1662,7 @@
     they are valid for the class).  Otherwise, the property
     is set to the form value.
 
-    For Date(), Interval(), Boolean(), and Number()
+    For Date(), Interval(), Boolean(), Integer() and Number()
     properties, the form value is converted to the
     appropriate
 

Roundup Issue Tracker: http://roundup-tracker.org/