aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/OpenSim/Data/SQLite/Resources/RegionStore.migrations (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Fix sqlite migration problems by moving migrations in 019_RegionStore.sql ↵Justin Clark-Casey (justincc)2010-09-011-3/+14
| | | | | | and 020 into RegionStore.migrations This shows that panda is still not running the sqlite database tests since this change fixes the test failure in that area when "nant test" is executed locally
* Implements parcel media setting persistence and packet / CAPS handlingJonathan Freedman2010-08-301-0/+10
| | | | | | properly for the new media settings. Signed-off-by: Melanie <melanie@t-data.com>
* remove estate stuff in sqlite region migrations since this also exists in ↵Justin Clark-Casey (justincc)2010-06-041-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 testsJustin Clark-Casey (justincc)2010-06-041-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!)AlexRa2010-05-231-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 formatAlexRa2010-05-161-0/+526