Base solution for your next web application
Open Closed

FYI MySQL Index length bug - fix #955


User avatar
0
paulbackhouse created

I managed to complete the upgrade to 0.8.0.3 and finally resolve the EF missing cmdlet problem - fix by the way is rollback EF to 6.1.1 and everything works perfectly with latest ABP stuff :) cmds are back (i.e add-migrations)

anyway, FYI. In the migration script, the Table "AbpUserLoginAttempts" tries to create and index on TenancyName, UserNameOrEmailAddress and Result. It will fail in MySql due to max length exceeding in the index (ref: <a class="postlink" href="http://stackoverflow.com/questions/8746207/1071-specified-key-was-too-long-max-key-length-is-1000-bytes">http://stackoverflow.com/questions/8746 ... 1000-bytes</a>)

To fix, change the length of the column UserNameOrEmailAddress from varchar(256) to varchar(255). 255 is the max default index capacity.

In case you want to put that in next release for MySql users


1 Answer(s)
  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi,

    Glad to hear that your problem is solved. Thanks for the information, we will fix it <a class="postlink" href="https://github.com/aspnetboilerplate/module-zero/issues/180">https://github.com/aspnetboilerplate/mo ... issues/180</a>