Mercurial > p > roundup > code
comparison doc/FAQ.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 | 609edf9de0a5 |
| children | 96dc9f07340a |
comparison
equal
deleted
inserted
replaced
| 5066:d2256fcfd81f | 5067:e424987d294a |
|---|---|
| 202 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | 202 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 203 | 203 |
| 204 When we sort items in the hyperdb, we use one of a number of methods, | 204 When we sort items in the hyperdb, we use one of a number of methods, |
| 205 depending on the properties being sorted on: | 205 depending on the properties being sorted on: |
| 206 | 206 |
| 207 1. If it's a String, Number, Date or Interval property, we just sort the | 207 1. If it's a String, Integer, Number, Date or Interval property, we |
| 208 scalar value of the property. Strings are sorted case-sensitively. | 208 just sort the scalar value of the property. Strings are sorted |
| 209 case-sensitively. | |
| 209 2. If it's a Link property, we sort by either the linked item's "order" | 210 2. If it's a Link property, we sort by either the linked item's "order" |
| 210 property (if it has one) or the linked item's "id". | 211 property (if it has one) or the linked item's "id". |
| 211 3. Mulitlinks sort similar to #2, but we start with the first | 212 3. Mulitlinks sort similar to #2, but we start with the first |
| 212 Multilink list item, and if they're the same, we sort by the second item, | 213 Multilink list item, and if they're the same, we sort by the second item, |
| 213 and so on. | 214 and so on. |