On 8/9/06, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
> A lot of prepared statements are emulated because db apps ( like
> mysql ) didn't really support a prepare until recently, and few db
> drivers supported an actual server side prepare. DBD::Pg just
> emulated it until 1.4 by using internal r
On Aug 9, 2006, at 8:34 AM, John Siracusa wrote:
> Yeah, although many places use prepare_cached() instead. This
> choice can be
> controlled on per-class and per-call basis. Grep the docs for
> "prepare_cached" and "dbi_prepare_cached" to learn more.
ok. that works.
>> if so, does it DEAL
On Wed, 2006-08-09 at 01:38 -0400, Jonathan Vanasco wrote:
> if so, does it DEALLOCATE the statement handle?
Won't that be the same as just turning off server-side statement
handles?
- Perrin
-
Using Tomcat but need to do m
On 8/7/06, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
> is there any way to do:
>
> query=> [
> first_name=> { lower=> 'john' },
> last_name=> { upper=> 'DOE' },
> ]
>
> becomes:
>
> SELECT t1.name FROM useraccount t1 WHERE lower(t1.first_name)= ?
> AND upper(t1.last_name)= ?
Right now you ha
On 8/9/06 6:35 AM, Danial Pearce wrote:
> Kind of off topic, but I was just looking to do some case insensitive
> searching myself and couldn't figure it out. I remembered this post
> mention ILIKE and it magically worked. I notice it's not in the
> QueryManager docs as a supported OP type though.
On 8/9/06 1:38 AM, Jonathan Vanasco wrote:
> a- does rose call any DBI prepares
> dbh->prepare(xxx)
> dbh->execute(xxx)
Yeah, although many places use prepare_cached() instead. This choice can be
controlled on per-class and per-call basis. Grep the docs for
"prepare_cached" and "dbi_prepare_cach
> > query=> [
> > first_name=> { lower=> 'john' },
> > last_name=> { upper=> 'DOE' },
> > ]
>
> just to add-- i know i can approximate that with an ILIKE and then
> parse the result set. i'm looking to specify the case on certain
> things though.
Kind of of
