Fabien O'Carroll f1ef801b78 🐛 Fixed error when during migration to 2.32.0 on mysql (#11208) ... closes #11207 MySQL doesn't allow unqiue keys with a length of more than 191 when using InnoDB with utfmb4. These changes will ensure any incorrect tables created are fixed and have the correct length for customer_id * Changed `customer_id` to non-unique column * Nooped the 2.32 `members_stripe_customers` migration * Added migration to recreate `members_stripe_customers` table * sqlite doesn't allow `ALTER TABLE` queries so this is the cleanest solution considering the table is not yet in use		2019-10-08 11:07:29 +01:00
..
1.3
1.4
1.5
1.7
1.9
1.13
1.18
1.19
1.20
1.21
1.22
1.25
2.0
2.2	Fixed "Unable to update nested relation" errors when rolling back migrations	2019-08-20 11:20:52 +01:00
2.3
2.6
2.8
2.13
2.14
2.15
2.16	Removed 2.16 member permission migration	2019-05-02 17:31:38 +02:00
2.17	Checked null & undefined in settings migration (#10609)	2019-03-13 23:35:23 +01:00
2.18	Enhanced 2.18 detection (#10610)	2019-03-13 23:40:50 +01:00
2.21	Added notification access persmission for users of Editor role	2019-04-18 13:02:23 +02:00
2.22	Copied member permission migration from 2.16->2.22	2019-05-02 17:31:38 +02:00
2.27	Fixed "Unable to update nested relation" errors when rolling back migrations	2019-08-20 11:20:52 +01:00
2.28	Fixed "Unable to update nested relation" errors when rolling back migrations	2019-08-20 11:20:52 +01:00
2.29	No-op'd post.page->post.type migrations, added cleanup post.type->post.page migrations	2019-08-19 12:02:14 +01:00
2.31	Removed name and password columns from members table	2019-09-05 11:14:50 +08:00
2.32	🐛 Fixed error when during migration to 2.32.0 on mysql (#11208)	2019-10-08 11:07:29 +01:00
2.33	🐛 Fixed error when during migration to 2.32.0 on mysql (#11208)	2019-10-08 11:07:29 +01:00