Is there a reason why the config table doesn't have a unique key defined for its data?
The reason for me asking is that on multiple ocassions, I've worked with clients having problems performing upgrades to more current versions of Sugar and I've noted that they had duplicate rows in the config table, usually the version row. I recently saw a case where just about all the rows were duplicated.
I have no idea what causes it, but it is rather cumbersome to clean up.
Would be nice if there was unique ID for each row, so one could at least clean it up manually through phpMyAdmin, SQLyog or other MySQL admin utility much easier.


LinkBack URL
About LinkBacks



Reply With Quote
Bookmarks