On Wed, Feb 19, 2003 at 01:45:06PM +0100, Daniel Rahn wrote:
And what might be the big features that you need and that would end in multiple SQL statements instead of one? Don't get me wrong. I just want to know what it is that you need. Joins etc. are defined in the standard and are no problem, subselects aren't either. What do you need exactly?
I don't have anything specific in mind, I just know the limitations of MySQL regarding to subselects (okay, in the latest 4.1 alpha alpha they implemented them), this might bite in the future. I just want to get sure that we don't run into problems somewhere in the future. OTOH joins are very very ressources consuming (I've seen a large join by a webdesigner who killed the informix optimizer...). It isn't really an issue now, but I can imagine that I'd need to split up some of the bigger joins into multiple SELECT to enahnce performance on our system. -- Regards, Wiktor Wodecki