[wp-trac] [WordPress Trac] #11649: Upgrades Fail Because of [11883]

[WordPress Trac]

#11649: Upgrades Fail Because of [11883]
-----------------------------+----------------------------------------------
 Reporter:  miqrogroove      |       Owner:           
     Type:  defect (bug)     |      Status:  new      
 Priority:  normal           |   Milestone:  2.9.1    
Component:  Upgrade/Install  |     Version:  2.9      
 Severity:  blocker          |    Keywords:  has-patch
-----------------------------+----------------------------------------------

Comment(by hakre):

 Replying to [comment:2 miqrogroove]:
 > Yes it's a cute one-word workaround
 Please tell that the admin who was reporting DISTINCT working in the
 forums. I only put that into a patch file since this ticket seemed
 important and the original reporter did not provide any more info /
 suggestions.

 > 2.9.1 should fix the problem not the symptom.
 Absolutely.

 Q:  How does ''11649-proper.patch'' preserve the option with the highest
 ID?

 Ups, I smeel a bit dataloss with your suggestion....

 ----

 I thought over this now for some hours: The actual problem is not the
 select query but not having enough memory later on. Which means that
 results should be free'd. Might be the case anyway that the MySql database
 optimizes the query by it's own and we do not need to change it (in the
 meaning of that it's not the cause of the symptom).

 Or am I wrong that those people in the forums all the time talk about
 memory problems? Or was it just guessed that the query is the cause of the
 problem and this has not verified yet?

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/11649#comment:5>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software