iamvela - 5:27 am on Apr 16, 2009 (gmt 0)

ok, I suppose we can upgrade our MySQL. Any known gotchas with that?

But it still bothers me that this issue has eaten up days & days of my brain cycles and is till unresolved... especially given that you you are doing the exact same thing without any problems really bugs me!

Y'know what else we figured out: e.g. when doing a join with another table instead of JOINING on OFFENDING_TABLE.id we joined on OFFENDING_TABLE.id+0 it spits the results right back! Voila!

Basically what we did was force it to not use the index for this table... by using a math operator: 0 in this example. Hopefully someone else can learn/benefit from this too :)

What is the URL to your app? Rgds,
--