Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | remove estate stuff in sqlite region migrations since this also exists in ↵ | Justin Clark-Casey (justincc) | 2010-06-04 | 1 | -54/+1 |
| | | | | | | estate migrations, change Sandbox to sandbox in sqlite region migrations re-enabling the sqlite data tests revealed these errors! | ||||
* | add sqlite database back to database tests | Justin Clark-Casey (justincc) | 2010-06-04 | 1 | -1/+1 |
| | | | | | this appears to be okay even though we reuse it between runs without deleting it first. size of the database appears not to be changing though that could be deceptive | ||||
* | Split migrations for RegionStore and EstateStore (see WARNING!) | AlexRa | 2010-05-23 | 1 | -25/+0 |
| | | | | | | | | | | | | ok, so the estate stores now want their own migration files, but as it happened the SQL definition were inside the Region migrations. It seems better/cleaner to keep each 'store' separately updatable. WARNING: any editing in the middle of the migration scripts (as opposite to just appending to them) has the potential of messing up updates of existing databases. As far as I can see, this one is (probably) safe, the worst that could happen is the EstateStore migration silently fail if the estate the tables are already there. | ||||
* | Migrations for SQLite converted to new format | AlexRa | 2010-05-16 | 1 | -0/+526 |