Mercurial > p > roundup > code
comparison doc/customizing.txt @ 2898:f203541b1116 maint-0.7
merge from HEAD
| author | Richard Jones <richard@users.sourceforge.net> |
|---|---|
| date | Thu, 11 Nov 2004 02:53:35 +0000 |
| parents | a204a49e0974 |
| children | 4129ecd31eea |
comparison
equal
deleted
inserted
replaced
| 2896:ab9e81b82db9 | 2898:f203541b1116 |
|---|---|
| 544 create(information) | 544 create(information) |
| 545 ~~~~~~~~~~~~~~~~~~~ | 545 ~~~~~~~~~~~~~~~~~~~ |
| 546 | 546 |
| 547 Create an item in the database. This is generally used to create items | 547 Create an item in the database. This is generally used to create items |
| 548 in the "definitional" classes like "priority" and "status". | 548 in the "definitional" classes like "priority" and "status". |
| 549 | |
| 550 | |
| 551 A note about ordering | |
| 552 ~~~~~~~~~~~~~~~~~~~~~ | |
| 553 | |
| 554 When we sort items in the hyperdb, we use one of a number of methods, | |
| 555 depending on the properties being sorted on: | |
| 556 | |
| 557 1. If it's a String, Number, Date or Interval property, we just sort the | |
| 558 scalar value of the property. Strings are sorted case-sensitively. | |
| 559 2. If it's a Link property, we sort by either the linked item's "order" | |
| 560 property (if it has one) or the linked item's "id". | |
| 561 3. Mulitlinks sort similar to #2, but we start with the first Multilink | |
| 562 list item, and if they're the same, we sort by the second item, and | |
| 563 so on. | |
| 564 | |
| 565 Note that if an "order" property is defined on a Class that is used for | |
| 566 sorting, all items of that Class *must* have a value against the "order" | |
| 567 property, or sorting will result in random ordering. | |
| 549 | 568 |
| 550 | 569 |
| 551 Examples of adding to your schema | 570 Examples of adding to your schema |
| 552 --------------------------------- | 571 --------------------------------- |
| 553 | 572 |