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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Added creator info across the board -- TaskInventoryItems and InventoryItems ↵	Diva Canto	2010-11-21	1	-0/+1
\| \| \| \| \| \|	themselves. Tested. Seems to be working, main tests pass. Nothing done for IARs or HG transfers yet -- this only works for OARs for the time being. New migration in inventory table in order to make CreatorID varchar(255).
*	Global creator information working on MySQL DB and on load/save OARs. ↵	Diva Canto	2010-11-21	1	-0/+8
\| \| \| \| \| \| \|	Creator name properly shown on the viewer as first.last @authority. New option added to save oar -profile=url. Migration on RegionStore making CreatorID be 255 chars. Moved Handling of user UUID -> name requests to a new module UserManagement/UserManagementModule.
*	Implements parcel media setting persistence and packet / CAPS handling	Jonathan Freedman	2010-08-30	1	-2/+12
\| \| \| \| \| \|	properly for the new media settings. Signed-off-by: Melanie <melanie@t-data.com>
*	add mysql support for media on a prim	Justin Clark-Casey (justincc)	2010-07-26	1	-1/+8
\|
*	* Deleted duplicated migration that was failing anyway.	Diva Canto	2010-06-14	1	-2/+0
\| \| \| \|	* Added an error message in initial estate owner creation that makes it clear what needs to happen.
*	Add the BEGIN; I had missed	Melanie	2010-06-09	1	-0/+1
\|
*	Re-add Migration version 32, which apparently got dropped completely.	Melanie	2010-06-09	1	-0/+72
\|
*	Add a migration to adjust types in the WL table. The new connector likes that	Melanie	2010-06-08	1	-0/+6
\| \| \| \|	better
*	MySQL Migrations: Minor correcton to Region/Estate split	AlexRa	2010-05-23	1	-6/+0
\| \| \| \|	(some Estate SQL left behind in the Region migration)
*	Split migrations for RegionStore and EstateStore (see WARNING!)	AlexRa	2010-05-23	1	-78/+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.
*	Cleaned up MySql migrations a bit more, got rid of all old-form migration ↵	Diva Canto	2010-05-20	1	-1/+4
\| \| \| \|	files. Restored Presence table to its taboo-breaking form.
*	Converted MySQL migration history to the new format	AlexRa	2010-05-16	1	-0/+806
	Replaced all NNN_StoreName.sql migration resources with a more readable, single-file-per-store