UbitUmarov 9b840f1f9e change the GetFallbackRegions sort code

2021-09-02 17:22:59 +01:00

..

AgentPrefs.migrations

…

AssetStore.migrations

Flatten migrations for MySQL.

2016-02-20 19:27:12 -08:00

AuthStore.migrations

Flatten migrations for MySQL.

2016-02-20 19:27:12 -08:00

Avatar.migrations

Correct case in the names of the Avatar and Friends tables

2016-03-24 16:43:27 -04:00

EstateStore.migrations

do store a new flag on region db

2020-06-09 19:44:57 +01:00

FriendsStore.migrations

a few more tables that may blowup on utf8mb4 and need no more than latin1

2020-12-16 01:46:11 +00:00

FSAssetStore.migrations

Bringing FSAssets more inline with current OpenSim standards. * If no connection string found in assets config, fallback to using default database config * Create database storage interface to allow other db connectors to be written at some point * Add MySQL migrations file to create the initial db table * Added new config option named DaysBetweenAccessTimeUpdates to reduce db load by only updating access times when fetching assets if the last access time was over the threshold. This idea was taken from XAssets service. * Change log message headers to indicate FS assets is the source not just assets

2015-07-12 04:03:08 +02:00

GridStore.migrations

Flatten migrations for MySQL.

2016-02-20 19:27:12 -08:00

GridUserStore.migrations

change some mysql tables and columns character sets, this is close to patch at mantis 8707, but that is not correct. This should have no impact on current dbs. Many of those are now too large to do this change automaticl,, but they should. Some columns as utf8 (4 bytes in future) are pure waste of space, in fact some are used as indexes and can violate max index size. Namelly on groups V2, reason why we are forced to use utf8mb3 mostly likely to be dropped by new mysql/maria versions

2020-11-14 17:21:10 +00:00

HGTravelStore.migrations

change some mysql tables and columns character sets, this is close to patch at mantis 8707, but that is not correct. This should have no impact on current dbs. Many of those are now too large to do this change automaticl,, but they should. Some columns as utf8 (4 bytes in future) are pure waste of space, in fact some are used as indexes and can violate max index size. Namelly on groups V2, reason why we are forced to use utf8mb3 mostly likely to be dropped by new mysql/maria versions

2020-11-14 17:21:10 +00:00

IM_Store.migrations

Create all tables ad InnoDB by default

2017-01-05 13:35:13 +00:00

InventoryStore.migrations

Flatten migrations for MySQL.

2016-02-20 19:27:12 -08:00

LogStore.migrations

…

MuteListStore.migrations

change some mysql tables and columns character sets, this is close to patch at mantis 8707, but that is not correct. This should have no impact on current dbs. Many of those are now too large to do this change automaticl,, but they should. Some columns as utf8 (4 bytes in future) are pure waste of space, in fact some are used as indexes and can violate max index size. Namelly on groups V2, reason why we are forced to use utf8mb3 mostly likely to be dropped by new mysql/maria versions

2020-11-14 17:21:10 +00:00

os_groups_Store.migrations

change some mysql tables and columns character sets, this is close to patch at mantis 8707, but that is not correct. This should have no impact on current dbs. Many of those are now too large to do this change automaticl,, but they should. Some columns as utf8 (4 bytes in future) are pure waste of space, in fact some are used as indexes and can violate max index size. Namelly on groups V2, reason why we are forced to use utf8mb3 mostly likely to be dropped by new mysql/maria versions

2020-11-14 17:21:10 +00:00

Presence.migrations

a few more tables that may blowup on utf8mb4 and need no more than latin1

2020-12-16 01:46:11 +00:00

RegionStore.migrations

change the GetFallbackRegions sort code

2021-09-02 17:22:59 +01:00

UserAccount.migrations

change some mysql tables and columns character sets, this is close to patch at mantis 8707, but that is not correct. This should have no impact on current dbs. Many of those are now too large to do this change automaticl,, but they should. Some columns as utf8 (4 bytes in future) are pure waste of space, in fact some are used as indexes and can violate max index size. Namelly on groups V2, reason why we are forced to use utf8mb3 mostly likely to be dropped by new mysql/maria versions

2020-11-14 17:21:10 +00:00

UserProfiles.migrations

Create all tables ad InnoDB by default

2017-01-05 13:35:13 +00:00

XAssetStore.migrations

…