opensim-SC_OLD - My fork of OpenSim for IG and MG, called SledjChisl.

	Commit message (Collapse)	Author	Files	Lines
2019-05-19	Various database fixups.	onefang	1	-6/+6
	InnoDB -> MyISAM utf8 if not exists white space
2019-05-19	Dump OpenSim 0.9.0.1 into it's own branch.	onefang	1	-48/+32

2016-11-03	MyISAM is still much better performing for OpenSim.	David Walter Seikel	1	-6/+6
	This time we got the file system asset server, even better still. B-)
2016-11-03	Initial update to OpenSim 0.8.2.1 source code.	David Walter Seikel	1	-6/+12

2013-02-23	MyISAM is much better performing for OpenSim.	David Walter Seikel	1	-6/+6

2012-01-22	Move Telehub tables and data from EstateSettings to RegionSettings.	Melanie	1	-21/+0
	This is damage control es EstateSettings is not the place this can be put. EstateSettings is nt unique to a region and therefore would introduce a hard limit of one telehub per estate, completely shutting off the option of having SL style telehubs, e.g. one per region. Whole estate teleport routing can still be implemented id desiresd, this way all options are open while the other way most options get closed off.
2012-01-21	Telehub Support:	BlueWall	1	-0/+21
	Telehub settings now persist to the database and are saved across sim restarts. So-far this only works on MySQL. this is a work in progress, teleport routing is not yet implemented.
2010-05-23	MySQL Migrations: Minor correcton to Region/Estate split	AlexRa	1	-0/+12
	(some Estate SQL left behind in the Region migration)
2010-05-23	Split migrations for RegionStore and EstateStore (see WARNING!)	AlexRa	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.