On 7/21/06, Ask Bjørn Hansen <[EMAIL PROTECTED]> wrote:
> 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.
>>
>> I
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
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 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
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,
