opensim-SC - My fork of OpenSim for IG and DG, called SledjChisl.

	Commit message (Collapse)	Author	Age	Files	Lines
*	MySQL default character set to utfmb4.	onefang	2021-08-17	1	-6/+6
\| \| \| \|	Coz on one box they defaulted to utfmb3, which .NET doesn't support.
*	Various database fixups.	onefang	2020-07-31	1	-6/+6
\| \| \| \| \| \| \|	InnoDB -> MyISAM utf8 if not exists white space
*	missing file	UbitUmarov	2019-08-17	1	-0/+7
\|
*	Flatten migrations for MySQL.	Diva Canto	2016-02-20	1	-48/+32
\| \| \| \| \| \|	Conflicts: OpenSim/Data/MySQL/Resources/RegionStore.migrations OpenSim/Data/MySQL/Resources/UserAccount.migrations
*	Send up the part missing from the Avination Estate commit.	Melanie	2013-05-11	1	-0/+6
\| \| \| \|	Warning - contains a small migration.
*	MySQL Migrations: Minor correcton to Region/Estate split	AlexRa	2010-05-23	1	-0/+12
\| \| \| \|	(some Estate SQL left behind in the Region migration)
*	Split migrations for RegionStore and EstateStore (see WARNING!)	AlexRa	2010-05-23	1	-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.