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 from the docs was that this would
> allow me to put arbitrary functions and such in here, like this:
>
> query => [ '1+1' => { sql => '2' } ]
The thing on the left has to be in one of the forms specified in the docs.
I guess it's not clear that when the docs say "column" they mean an actual
column, not arbitrary text. I'll clarify it in the next release.
> 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 used by RDBO in some cases,
but a "mode" where it causes a fatal error could be added (set by a param to
the call or a class attribute maybe)
-John
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Rose-db-object mailing list
Rose-db-object@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rose-db-object
