I finally bit the bind_param() bullet. The speed hit is minor, and
only applies when a class has one or more BYTEA columns in its table.
Still, to make amends, I hacked in a more efficient approach to
complex limit/offset queries. Only Postgres supports it right now,
but it's the most important o
I'm using the QueryBuilder from some of my code, and it has been working
quite well. I have a case where the behavior surprised me and I'm
wondering if I misunderstood the docs.
The docs show this:
query => [ legs => { gt_sql => 'eyes' } ]
This results in "legs > eyes" with no quoting. However,
On 7/21/06 6:14 PM, Perrin Harkins wrote:
> The docs show this:
> query => [ legs => { gt_sql => 'eyes' } ]
>
> This results in "legs > eyes" with no quoting. However, if "legs" is
> something other than a column name that the QueryBuilder knows, it just
> gets silently dropped. My impression fr
On Jul 21, 2006, at 15:21, John Siracusa wrote:
>> Also, it would be very nice if columns that don't match could
>> cause a fatal
>> error instead of being silently dropped. I will see if I can make
>> a patch for
>> that if you agree.
>
> IIRC, the existing "silent" behavior is actually use
On 7/21/06 7:33 PM, Ask Bjørn Hansen wrote:
> How about making the fatal error the default and then have RDBO pass
> a "drop columns silently" option?
Yeah, that seems reasonable.
-John
-
Take Surveys. Earn Cash. Influence
Posted on behalf of Jonathan Vanasco...
-- Forwarded Message
From: Jonathan <[EMAIL PROTECTED]>
Date: Fri, 21 Jul 2006 19:49:22 -0400
To: <[EMAIL PROTECTED]>
Subject: Where / Or question for manager class
I hate asking for this- but my idiot email provider just got rbl'd ,
so my list posts ar
On 7/21/06 7:55 PM, John Siracusa wrote:
> package myManager;
> sub user_search {
> my ( $class, %args )= @_ ;
> my @ors;
> foreach my $_or ( @{$args{'type_id'}} ) {
> push @or , { 'type_id'=> $_or };
Why is that pushing a hashref onto @or? I think it should just be:
push(@or, type_id
Has anyone built any tools for automating Rose::HTML::Object form classes
from Rose::DB::Object classes? In principle, it shouldn't be too hard to
do, but I just wanted to see if someone had already gone ahead with this,
before I start down the road of making my own.
Thanks,
Sean
--
