Mercurial > p > roundup > code
comparison doc/upgrading.txt @ 1596:33a0d94c7658
searching on ranges of intervals is implemented
| author | Andrey Lebedev <kedder@users.sourceforge.net> |
|---|---|
| date | Sun, 20 Apr 2003 11:58:45 +0000 |
| parents | 3f2e516b8de3 |
| children | 4a47eb555e51 |
comparison
equal
deleted
inserted
replaced
| 1595:1ae674595c04 | 1596:33a0d94c7658 |
|---|---|
| 68 | 68 |
| 69 - From version 0.6.0 roundup supports displaying of Date data in user' local | 69 - From version 0.6.0 roundup supports displaying of Date data in user' local |
| 70 timezone if he/she has provided timezone information. To make it possible | 70 timezone if he/she has provided timezone information. To make it possible |
| 71 some modification to tracker's schema and HTML templates are required. | 71 some modification to tracker's schema and HTML templates are required. |
| 72 First you should add string property 'timezone' to user class in dbinit.py | 72 First you should add string property 'timezone' to user class in dbinit.py |
| 73 like this: | 73 like this:: |
| 74 | 74 |
| 75 user = Class(db, "user", | 75 user = Class(db, "user", |
| 76 username=String(), password=Password(), | 76 username=String(), password=Password(), |
| 77 address=String(), realname=String(), | 77 address=String(), realname=String(), |
| 78 phone=String(), organisation=String(), | 78 phone=String(), organisation=String(), |
| 95 and mail interfaces in local time. It will also accept any Date info in | 95 and mail interfaces in local time. It will also accept any Date info in |
| 96 local time, convert and store it in GMT. | 96 local time, convert and store it in GMT. |
| 97 | 97 |
| 98 However you are not forced to make these modifications. By default roundup | 98 However you are not forced to make these modifications. By default roundup |
| 99 will assume timezone=0 and will work as previous versions did. | 99 will assume timezone=0 and will work as previous versions did. |
| 100 | |
| 101 | |
| 102 0.6.0 Notes for metakit backend users | |
| 103 ------------------------------------- | |
| 104 | |
| 105 - Roundup 0.6.0 introduced searching on ranges of dates and intervals. To | |
| 106 support it, some modifications to interval storing routine were made. So if | |
| 107 your tracker uses metakit backend and your db schema contains intervals | |
| 108 property, searches on that property will not be accurate for db items that | |
| 109 was stored before roundup' upgrade. However all new records should be | |
| 110 searchable on intervals. | |
| 111 | |
| 112 It is possible to convert your database to new format: you can export and | |
| 113 import back all your data (consult "Migrating backends" in "Maintenance" | |
| 114 documentation). After this operation all your interval properties should | |
| 115 become searchable. | |
| 116 | |
| 117 Users of backends others than metakit should not worry about this issue. | |
| 118 | |
| 100 | 119 |
| 101 Migrating from 0.4.x to 0.5.0 | 120 Migrating from 0.4.x to 0.5.0 |
| 102 ============================= | 121 ============================= |
| 103 | 122 |
| 104 This has been a fairly major revision of Roundup: | 123 This has been a fairly major revision of Roundup: |