UbitUmarov 9533217d82 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 4 vuotta sitten
..
AgentPrefs.migrations 6f71d5c2c6 Support for Linden AgentPreferences capability and friends (UpdateAgentLanguage and UpdateAgentInformation) and Mantis #7157 9 vuotta sitten
AssetStore.migrations 134e94a7e9 Flatten migrations for MySQL. 8 vuotta sitten
AuthStore.migrations 134e94a7e9 Flatten migrations for MySQL. 8 vuotta sitten
Avatar.migrations 2cfe848ceb Correct case in the names of the Avatar and Friends tables 8 vuotta sitten
EstateStore.migrations 0d76635113 do store a new flag on region db 4 vuotta sitten
FSAssetStore.migrations f3f748ed11 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 9 vuotta sitten
FriendsStore.migrations 2cfe848ceb Correct case in the names of the Avatar and Friends tables 8 vuotta sitten
GridStore.migrations 134e94a7e9 Flatten migrations for MySQL. 8 vuotta sitten
GridUserStore.migrations 9533217d82 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 4 vuotta sitten
HGTravelStore.migrations 9533217d82 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 4 vuotta sitten
IM_Store.migrations 53fe204eed Create all tables ad InnoDB by default 7 vuotta sitten
InventoryStore.migrations 134e94a7e9 Flatten migrations for MySQL. 8 vuotta sitten
LogStore.migrations ee713cb253 Converted MySQL migration history to the new format 14 vuotta sitten
MuteListStore.migrations 9533217d82 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 4 vuotta sitten
Presence.migrations 548b741130 Correct the case of the Presence table 8 vuotta sitten
RegionStore.migrations 44c90bf294 misspell all across the board 4 vuotta sitten
UserAccount.migrations 9533217d82 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 4 vuotta sitten
UserProfiles.migrations 53fe204eed Create all tables ad InnoDB by default 7 vuotta sitten
XAssetStore.migrations d7b45a3ed2 Alter the migrations so that it is a no-op as the columns are unused and the operation is very expensive 9 vuotta sitten
os_groups_Store.migrations 9533217d82 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 4 vuotta sitten