6 Commits

Author	SHA1	Message	Date
Diva Canto	d992779397	Switched order of SQL statements in Friends migration -- resulted in the wrong key	2011-06-11 09:36:57 -07:00
Diva Canto	c13acdf5a1	This is the better solution: make the combined key be only on the first 36 characters of each field -- that's the UUIDs. Thanks coyled. WARNING: Again, people who have gone through this migration and failed need to run it manually.	2011-06-01 20:19:22 -07:00
Diva Canto	43ecc46a22	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 3fa54a156a.	2011-06-01 20:09:59 -07:00
Diva Canto	3fa54a156a	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.	2011-06-01 20:02:26 -07:00
Diva Canto	d21e9c755f	HG Friends working to some extent: friendships offered and accepted correctly handled. Friends list showing correct foreign names. TODO: GrantRights.	2011-05-19 16:54:46 -07:00
AlexRa	ee713cb253	Converted MySQL migration history to the new format ... Replaced all NNN_StoreName.sql migration resources with a more readable, single-file-per-store	2010-05-16 17:04:13 +03:00