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

	Commit message (Collapse)	Author	Files	Lines
2013-10-16	* One More thing, add an appdomain data element to ensure that we don't ↵	Fernando Oliveira	1	-2/+8
	duplicate the assembly resolving.
2013-10-16	* Fixes mantis mantis 0006803 [PGSQL] - Simulator crashes - ↵	Fernando Oliveira	1	-0/+23
	Mono.Security.dll missing. The root of the issue is that the Postgres driver relies on Mono.Security.dll from the mono project. Unfortunately, when using Mono, including the dll in the distribution causes conflicts. This solution puts Mono.Security.dll in bin/lib/NET/ and, if windows .NET is the runtime, informs the assembly loader to load bin/lib/NET/Mono.Security.dll when .NET is scanning for the Mono.Security namespace. On Mono, the included Mono.Security assembly is ignored.
2013-10-12	Fernando Oliveira's Postgress SQL Server Data Connector as a single commit.	Fernando Oliveira	1	-6/+6
	* Added PostGreSQL support * Added MySQL/MySQLXGroupData.cs * PostgreSQL data access implementation * PostgreSQL dll binarie and RegionStore.migrations * Migrations Scripts from MSSQL to POSTGRES * Postgres SQL Type fixes * Postgres SQL Connection string * Data type issues * more fixes * tests and +tests * UUID x string - FIGHT! * Fixed PG types to internal csharp types * More data type fix (PostgreSQL fields are case sensitive) :( * more field case sensitive fixes * changed the migration files to be case sensitive for fields. * fixed fields case * finished converting, now search for hidden bugs. * some more fixes * bool type fixed * more case fixes; * creatorID case fixed * case fields fixed * fixed default now() for TMStamp fields with don't allow nulls. * fix case sensitve for Region name and Estate name * fixed case for names for search * fix class name Error * Bug fixed on select and migrations * Un-Reverting my change due to Postgres issue with the ILIKE function * Fixed some issued for Diva Distro * Fixes for integration with Diva Distro * Added System.Core to prebuild.xml for PG project * Configured to make DIff for Push to OpenSim Project * Diffs only to PostgreSQL mods.
2010-02-05	Updated MySQL connection management to use the MySQL connection pooling. ↵	Master ScienceSim	1	-49/+13
	This should accommodate various timeout problems that exist with the current connection pool code in a more general and standard way.
2009-11-02	Removing Console.WriteLine()s that were brought in with the revert	John Hurliman	1	-2/+0

2009-11-02	Reverting the memory leak patch for MySQL. Problems have been reported with ↵	John Hurliman	1	-8/+5
	the grid server after running for several hours
2009-10-06	Remove the using() constructs from the new style database modules; they caused	Melanie	1	-4/+10
	the underlying connection of a reader or command to be closed before the reader or command itself. Added the proper logic to Close and dispose items in CloseDBConnection. Readers and Connections need Close(), Commands need Dispose(), in the order Reader, Command, Connection. Also reinstated 80-column-friendly formatting
2009-10-05	Added CloseDBConnection() to replace the old CloseReaderCommand(). This will ↵	John Hurliman	1	-7/+7
	close the MySQLConnection attached to a MySQLCommand. I'm not sure if this accounts for every time a database connection needs to be closed, but it matches up 1:1 with the places where the database connection was previously being closed
2009-10-04	* MySQL data tests now pass by fixing a bad fix for a bad cast on the asset ↵	John Hurliman	1	-10/+4
	Local member in MySQLAssetData * First pass at applying the using(){} pattern to IDisposable objects. Always use the using pattern on IDisposable objects whenever possible, do not manually call .Close() or .Dispose() unless there is no other way to write the code. This pass mostly covers OpenSim.Data.MySQL, and should have no functional change (tests still pass)
2009-09-04	More work on new authentication service	Melanie	1	-0/+8

2009-09-04	Add the user authentication data adapter. This is meant to use a new table	Melanie	1	-0/+115
	schema, but can read the old ones for compatibility. It should not be used to write to the old tables unless you know what you're doing! This is untested and will probably not work.