aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/ThirdPartyLicenses
diff options
context:
space:
mode:
authorDiva Canto2011-06-01 20:09:59 -0700
committerDiva Canto2011-06-01 20:09:59 -0700
commit43ecc46a224d07661af42379f12f394e1bd873fd (patch)
tree366e1f63d0c5503a57981fa08f3213725f88be31 /ThirdPartyLicenses
parentChanged Friends table to have 165-sized varchars on PrincipalID and FriendID.... (diff)
downloadopensim-SC_OLD-43ecc46a224d07661af42379f12f394e1bd873fd.zip
opensim-SC_OLD-43ecc46a224d07661af42379f12f394e1bd873fd.tar.gz
opensim-SC_OLD-43ecc46a224d07661af42379f12f394e1bd873fd.tar.bz2
opensim-SC_OLD-43ecc46a224d07661af42379f12f394e1bd873fd.tar.xz
It looks like there's a better solution for that problem.
Revert "Changed Friends table to have 165-sized varchars on PrincipalID and FriendID. The reason for this number is the following: there is a combined key of these 2 fields; apparently MySql can't handle keys larger than 1000 bytes; when the table is created with utf8 encoding, this combined key is bigger than 1000 bytes, and the migration fails. WARNING: this is not a new migration! People who have gone through this migration and failed should update the sizes of these fields manually." This reverts commit 3fa54a156a83e498a7d5d0949a5f848fe82fe86f.
Diffstat (limited to 'ThirdPartyLicenses')
0 files changed, 0 insertions, 0 deletions