> > I have no idea if the MySQL folks are making up this syntax or got it > from some standard--but I'm not happy with it. >
I think it's mysql specific > Barring all this--I'm trying to figure out how to do it on top of > Recordset, but that's not easy either. Basically I need to check all > the arguments that might be handed to Search, figure out how they are > going to impact the search, and then construct my own search. (In > other words, I need to know whether they passed '$fields' or not, > since I need to do *,match... if they didn't, otherwise I'd just add > 'match...' to the $fields hash. > > But then I run into problem because Recordset certainly isn't going > to recognize 'match(...)' as a field name, so it will discard it. > You can prefix any field name with a \, then Recordset will let it unmodified through > At this point I think I'm just going to have to bypass Recordset > entirely for this case. I don't suppose there's any way of getting > the SQL statement that Recordset is going to use before it uses it, > and modifying it? > No, also this shouldn't be to hard to implement. The problem arises for any sort of database functions. You can pass them through Recordset, but Recordset doesn't handle them in any way at the moment. Gerald ------------------------------------------------------------- Gerald Richter ecos electronic communication services gmbh Internetconnect * Webserver/-design/-datenbanken * Consulting Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131 WWW: http://www.ecos.de Fax: +49 6133 925152 ------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
