6 Commits

Author	SHA1	Message	Date
UbitUmarov	0d76635113	do store a new flag on region db	2020-06-09 19:44:57 +01:00
UbitUmarov	115d69e633	missing file	2019-08-17 23:59:01 +01:00
Diva Canto	134e94a7e9	Flatten migrations for MySQL. ... Conflicts: OpenSim/Data/MySQL/Resources/RegionStore.migrations OpenSim/Data/MySQL/Resources/UserAccount.migrations	2016-02-20 19:27:12 -08:00
Melanie	81d8deb1a8	Send up the part missing from the Avination Estate commit. ... Warning - contains a small migration.	2013-05-11 01:27:37 +01:00
AlexRa	05d9ca1b26	MySQL Migrations: Minor correcton to Region/Estate split ... (some Estate SQL left behind in the Region migration)	2010-05-23 11:48:28 +03:00
AlexRa	ebc2b6d4f6	Split migrations for RegionStore and EstateStore (see WARNING!) ... 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.	2010-05-23 11:48:16 +03:00