Claudia M Posted June 16, 2018 Share Posted June 16, 2018 Hi, I just upgraded to CC6.2.1. and was checking advanced/maintenance/database and this orange error was still there in order_summary. I thought this was going to be fixed in the new upgrade. Thanks in advance. Me Quote Link to comment Share on other sites More sharing options...
bsmither Posted June 16, 2018 Share Posted June 16, 2018 According to the history of this code in the Github, the change to the schema had to be backed out because empty values (or null) would be in multiple rows - and that is not allowed for a UNIQUE column. I suppose what should have happened is that the expected schema description should have been updated to not show any discrepancy. Quote Link to comment Share on other sites More sharing options...
Dirty Butter Posted June 16, 2018 Share Posted June 16, 2018 So exactly what should it be set to? I have INDEX when I edit it. Is that right? Quote Link to comment Share on other sites More sharing options...
bsmither Posted June 16, 2018 Share Posted June 16, 2018 It is worthwhile to have an INDEX against that column. Just not UNIQUE. Quote Link to comment Share on other sites More sharing options...
Claudia M Posted June 16, 2018 Author Share Posted June 16, 2018 How do I do that Brian if it's not automatically like that? Quote Link to comment Share on other sites More sharing options...
bsmither Posted June 16, 2018 Share Posted June 16, 2018 I don't use phpMyAdmin that often, but it should not be difficult to find where to add such an index. On the other hand, if one doesn't use any custom order id indicators, just ignore this. Quote Link to comment Share on other sites More sharing options...
Claudia M Posted June 16, 2018 Author Share Posted June 16, 2018 Then I'm just going to leave it alone. Quote Link to comment Share on other sites More sharing options...
bsmither Posted June 17, 2018 Share Posted June 17, 2018 According to CC621 /setup/db/upgrade/6.2.1.sql, there is: ALTER TABLE `CubeCart_order_summary` ADD KEY (`custom_oid`); Then, in CC621 (as compared to CC620), in admin /sources/maintenance.index.inc.php, line 808: 'custom_oid' => 'KEY' (was: 'custom_oid' => 'UNIQUE KEY') So, please verify that your admin file /sources/maintenance.index.inc.php, line 808 is correct. Quote Link to comment Share on other sites More sharing options...
Claudia M Posted June 17, 2018 Author Share Posted June 17, 2018 (edited) Here is my lines 806 - 808 'email' => 'KEY', 'order_date' => 'KEY', 'custom_oid' => 'KEY' I was looking at the structure of my order_summary in the database and I think, I don't really remember, when this first came up I tried to fix this according to the previous post, but I think I put it back to how it was. Should I do something with this? Here's what thee line looks like: Edited June 17, 2018 by Claudia M More info Quote Link to comment Share on other sites More sharing options...
bsmither Posted June 17, 2018 Share Posted June 17, 2018 "custom_oid" has a regular KEY and that's good. At some time, a second occurance of adding a KEY index happened, creating "custom_oid_2". Maybe running the setup script a second time? Anyway, you may delete the "custom_oid_2" index. Lines 806-808 are correct for CC621. The question then becomes, from where did CubeCart get information that the column "custom_oid" is expected to have a UNIQUE KEY. Quote Link to comment Share on other sites More sharing options...
Claudia M Posted June 17, 2018 Author Share Posted June 17, 2018 " The question then becomes, from where did CubeCart get information that the column "custom_oid" is expected to have a UNIQUE KEY. " I think this was something I did awhile back, before the upgrade, trying to fix the orange error message. What should I do? I'll delete the custom_oid_2 right now. Quote Link to comment Share on other sites More sharing options...
Claudia M Posted June 17, 2018 Author Share Posted June 17, 2018 The orange error is gone. I clicked the index button next to the custom_oid. This is what I have now. Is there anything I need to do? Quote Link to comment Share on other sites More sharing options...
bsmither Posted June 17, 2018 Share Posted June 17, 2018 You are good to go. Quote Link to comment Share on other sites More sharing options...
Claudia M Posted June 17, 2018 Author Share Posted June 17, 2018 Thanks Brian! 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.