Claudia M Posted May 13, 2018 Share Posted May 13, 2018 (edited) I'm running 6.2.0. I got this in admin/maintainence / database but in looking in the order_summary table with phpMyAdmin I don't have a custom_oid that I saw. How do I fix this error? Thanks in advance, - Me This is what I have: Edited May 13, 2018 by Claudia M Quote Link to comment Share on other sites More sharing options...
bsmither Posted May 13, 2018 Share Posted May 13, 2018 The phpMyAdmin should have the means to create keys on a table. From the image above, perhaps you check the box to the left of custom_oid, then With selected:, click Index. The programmers were in error to have the custom_oid column be a UNIQUE KEY. CubeCart 6.2.1 will advise on having a KEY, but not a UNIQUE KEY, if no key exists. Quote Link to comment Share on other sites More sharing options...
Claudia M Posted May 13, 2018 Author Share Posted May 13, 2018 I did what you suggested but still get the orange error message. Cleared cache. This is what I have now. Quote Link to comment Share on other sites More sharing options...
Al Brookbanks Posted May 13, 2018 Share Posted May 13, 2018 1 hour ago, bsmither said: The phpMyAdmin should have the means to create keys on a table. From the image above, perhaps you check the box to the left of custom_oid, then With selected:, click Index. The programmers were in error to have the custom_oid column be a UNIQUE KEY. CubeCart 6.2.1 will advise on having a KEY, but not a UNIQUE KEY, if no key exists. Exactly right. Quote Link to comment Share on other sites More sharing options...
Claudia M Posted May 13, 2018 Author Share Posted May 13, 2018 If this is correct why do I still have the orange error message in admin/maintenance/database and should I worry about it? Quote Link to comment Share on other sites More sharing options...
Al Brookbanks Posted May 13, 2018 Share Posted May 13, 2018 Because it's told to look for a wrong value. Please ignore it. After the next update it will be gone and if not the error message will be correct. Quote Link to comment Share on other sites More sharing options...
Claudia M Posted May 13, 2018 Author Share Posted May 13, 2018 Ok Al ... Thanks Quote Link to comment Share on other sites More sharing options...
havenswift-hosting Posted May 14, 2018 Share Posted May 14, 2018 I have noticed that while the custom_oid column does exist, on every site we have upgraded to 6.2.0 the index doesnt. The only exceptions are the couple that we upgraded to the beta and RC versions first. Quote Link to comment Share on other sites More sharing options...
Al Brookbanks Posted May 14, 2018 Share Posted May 14, 2018 That's because after it is created the column initialises with a default empty value. This can't be unique and therefore the latter query to create a unique key fails. Quote Link to comment Share on other sites More sharing options...
havenswift-hosting Posted May 14, 2018 Share Posted May 14, 2018 Yes exactly and mentioned it to ensure that it will be dealt with as part of 6.2.1 - but just checked the 6.2.1 db upgrade script and see you are dropping and recreating the index so all good Quote Link to comment Share on other sites More sharing options...
Al Brookbanks Posted May 14, 2018 Share Posted May 14, 2018 Already has. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.