Re: Name for new function

On Mon, 17 Jul 2000, Derick Rethans wrote: > Hi, > > Zeev Suraski wrote: > > > As I pointed out, I tend to think the same. This should be done in > > user-space, until there's 'true' support for sub-selects in MySQL. > > Subselects are on MySQL's TODO lists for several *years* now and I don't think > it will be implemented soon. What's the problem (besides it actually belongs > in the MySQL server part) with a self-contained extension (now called > db_layer) which implements this function? It doesn't clutter up the MySQL part > of the code, and it's easy maintainable. > > I still agree that the best thing to do is to write to code into the > MySQL-server, but I never saw such a mess of code. :-) db_layer? And that would be MySQL specific extension? Doesn't make much sense to me to introduce extension namespace pollution if it's only for 1 function that is database specific. -Andrei "In My Egotistical Opinion, most people's C programs should be indented six feet downward and covered with dirt." -- Blair P. Houghton