Geir Nøklebye 653b896794 PGSQL: Update simulation data with a number of missing fields for parcels. Some of the fields should probably be migrated to type Boolean to avoid the hairy casting in the query. In addition the overall server code relies in the Replace in SQL statement that is proprietary to MySQL, so the PGSQL code is rather unsafe as it is. Should probably set a transaction on the whole operation so that if something goes wrong the database record is not zapped as it is now. PostgreSQL 9.5 has the upsert functionality which would bring the code closer to the MySQL version. This commit also has an update to PGSQLRegionData ...

Signed-off-by: UbitUmarov <ajlduarte@sapo.pt>

2016-07-15 15:45:39 +01:00

..

Properties

Pushed AssemblyVersion up to VersionInfo, so that we don't need to do global replace anymore.

2016-02-21 11:14:02 -08:00

Resources

POSTGRES: Update database migrations to be in accordance with MySQL table definitions. Prerequisite for fixing PGSQLSimulationdata

2016-04-25 12:17:17 -04:00

PGSQLAgentPreferencesData.cs

Updated the code to handle Agent Preferences. Thanks to TomDataworks for providing a final solution.

2016-04-25 12:15:34 -04:00

PGSQLAssetData.cs

bad merge?

2015-09-01 14:54:35 +01:00

PGSQLAuthenticationData.cs

…

PGSQLAvatarData.cs

…

PGSQLEstateData.cs

Thanks Gavin Hird for a fix for an exception when requesting an Estate Ban when using PGSQL.

2015-06-24 03:46:30 -07:00

PGSQLFramework.cs

* One More thing, add an appdomain data element to ensure that we don't duplicate the assembly resolving.

2013-10-16 21:20:11 -05:00

PGSQLFriendsData.cs

Eliminated many warnings

2014-04-23 16:37:36 +03:00

PGSQLGenericTableHandler.cs

Fix Mantis #7805, table handler needs to look for all unique constraints.

2016-04-25 12:11:03 -04:00

PGSQLGridUserData.cs

…

PGSQLGroupsData.cs

Update PGSQL groups handler to accept search queries from the viewer

2015-07-26 11:59:15 +01:00

PGSQLHGTravelData.cs

…

PGSQLInventoryData.cs

…

PGSQLManager.cs

Updated the code to handle Agent Preferences. Thanks to TomDataworks for providing a final solution.

2016-04-25 12:15:34 -04:00

PGSQLMigration.cs

…

PGSQLOfflineIMData.cs

…

PGSQLPresenceData.cs

Update PGSQL groups handler to accept search queries from the viewer

2015-07-26 11:59:15 +01:00

PGSQLRegionData.cs

PGSQL: Update simulation data with a number of missing fields for parcels. Some of the fields should probably be migrated to type Boolean to avoid the hairy casting in the query. In addition the overall server code relies in the Replace in SQL statement that is proprietary to MySQL, so the PGSQL code is rather unsafe as it is. Should probably set a transaction on the whole operation so that if something goes wrong the database record is not zapped as it is now. PostgreSQL 9.5 has the upsert functionality which would bring the code closer to the MySQL version. This commit also has an update to PGSQLRegionData

2016-07-15 15:45:39 +01:00

PGSQLSimulationData.cs

PGSQL: Update simulation data with a number of missing fields for parcels. Some of the fields should probably be migrated to type Boolean to avoid the hairy casting in the query. In addition the overall server code relies in the Replace in SQL statement that is proprietary to MySQL, so the PGSQL code is rather unsafe as it is. Should probably set a transaction on the whole operation so that if something goes wrong the database record is not zapped as it is now. PostgreSQL 9.5 has the upsert functionality which would bring the code closer to the MySQL version. This commit also has an update to PGSQLRegionData

2016-07-15 15:45:39 +01:00

PGSQLUserAccountData.cs

bad merge?

2015-09-01 14:54:35 +01:00

PGSQLUserProfilesData.cs

PGSQL migrations for IM_Store, UserProfiles, removal of casting exception for UserProfiles and adding double precision to PGSQL Manager

2015-07-31 15:57:22 +01:00

PGSQLXAssetData.cs

Touchup PgSQL XAssets adapter

2014-10-15 17:28:51 -04:00

PGSQLXInventoryData.cs

…