Re: DB_DataObject: support for LIKE expressions
| From: | mitchell perilstein | Date: | Sat, 18 Jan 2003 21:56:32 +0000 |
| Subject: | Re: DB_DataObject: support for LIKE expressions | ||
| References: | 1 2 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-3343@lists.php.net to get a copy of this message | ||
Hi Stijn,
Thanks for looking at the patch. ((Thanks also to you and Alan for
looking at the id==id issue with addJoin. I have my workaround on that
issue so it's not a problem for me at this point, just wanted the group
to be aware.))
On Sat, 2003-01-18 at 14:04, Stijn de Reede wrote:
> I dunno if this should be in the main release. IMHO it complicates
> things, and certainly doesn't make DB_DataObject easier to use.
I agree, it's not tested and it does complicate the API. But at the same
time I don't know what is an appropriate place and time for such a thing.
in the pear roadmap.
> Setting
> the option in to ini file isn't a good idea either, because I think you
> might want to change behaviour mid-script. In my opinion this should not
> be done at such a low level as DB_DataObject is.
I don't understand this; can't you just adjust options in memory any time
after you parse_ini_file() and put the options in a global? If you are
suggesting a per-call option override, well, that would really complicate
the API, wouldn't it!?
Regarding DB_DataObject being low-level: where in Pear would be an apppropriate
place to form queries that are not supported by the xxxAdd() methods? I thought
about overriding whereAdd in my subclasses, but once he adds the '=' operator
there's no way. On the other hand, one could use query() for everything, but
then why have the xxxAdd methods if that were the intent?
Best regards, and thanks for all the code!
- Mitch