aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/OpenSim/Data/MySQL/Resources/EstateStore.migrations (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Various database fixups.onefang2019-05-191-6/+6
| | | | | | | InnoDB -> MyISAM utf8 if not exists white space
* Dump OpenSim 0.9.0.1 into it's own branch.onefang2019-05-191-48/+32
|
* MyISAM is still much better performing for OpenSim.David Walter Seikel2016-11-031-6/+6
| | | | This time we got the file system asset server, even better still. B-)
* Initial update to OpenSim 0.8.2.1 source code.David Walter Seikel2016-11-031-6/+12
|
* MyISAM is much better performing for OpenSim.David Walter Seikel2013-02-231-6/+6
|
* MySQL Migrations: Minor correcton to Region/Estate splitAlexRa2010-05-231-0/+12
| | | | (some Estate SQL left behind in the Region migration)
* Split migrations for RegionStore and EstateStore (see WARNING!)AlexRa2010-05-231-0/+69
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.