J3.x talk

Insert error in menu table of migrated data

From Joomla! Documentation

Revision as of 02:51, 18 August 2013 by Sovainfo (Talk | contribs)

Wouldn't waste time on this, see Sovainfo (talk) 08:47, 16 August 2013 (CDT)

Thanks Sovainfo. Yes, I broke it out of the Upgrading page. The pull request you referenced will make it into 3.2 and at that point it should be a non-issue for people upgrading to 3.2+ versions from 2.5. I see you also posted to the forum article where this came from originally. IMO, what we really need is a script to correct all the problems with the ids, move the user created ones and search for missing missing core menus. Thanks again. Tom Hutchison (talk) 19:37, 16 August 2013 (CDT)

Consider that the wrong solution! Stop abusing the rdbms. There should be no other meaning attached to the id. In relational speak, you need an attribute that contains that information. Combining information is not done in the relational world. Sofar I haven't seen any requirement for identifying cms delivered menuitems apart from user added menuitems. If there is, you need to add an attribute, not putting meaning in the sequence number. The solution is to remove the id from the column list and its value from the values list. Sovainfo (talk) 03:03, 17 August 2013 (CDT)

Before my time why the ids were hard coded in so I have no idea the thought behind it or the thought of why it was needed. We need to deal with what we have, how to fix the existing problems and then move forward. If you have a solution, I invite you to submit a pull request. Thanks Tom Hutchison (talk) 09:01, 17 August 2013 (CDT)

There is no need for another pull request. PR1722 solves it. At least when they stop using fixed numbers. That solution is also provided on the forum (just removing id from INSERT). So, there is no need for the procedure described in this document. Hopefully others will understand! Sovainfo (talk) 02:51, 18 August 2013 (CDT)