BTW, I put the new "distinct" and "fetch_only" manager parameters in CVS
last night. They'll probably go out in the next release, assuming no big
problems are discovered.
Here are the docs (from Rose::DB::Object::Manager):
---
=item C<distinct [BOOL|ARRAYREF]>
If set to any kind of true value, then the "DISTINCT" SQL keyword will be
added to the "SELECT" statement. Specific values trigger the behaviors
described below.
If set to a simple scalar value that is true, then only the columns in the
primary table ("t1") are fetched from the database.
If set to a reference to an array of table names or "tN" table aliases, then
only the columns from those tables will be fetched. Columns from the
primary table ("t1") are always selected, regardless of whether or not it
appears in the list.
This parameter conflicts with the C<fetch_only> parameter in the case where
both provide a list of table names or aliases. In this case, if the value
of the C<distinct> parameter is also reference to an array table names or
aliases, then a fatal error will occur.
=item C<fetch_only [ARRAYREF]>
ARRAYREF should be a reference to an array of table names or "tN" table
aliases. Only the columns from those tables will be fetched. Columns from
the primary table ("t1") are always selected, regardless of whether or not
it appears in the list.
This parameter conflicts with the C<distinct> parameter in the case where
both provide a list of table names or aliases. In this case, then a fatal
error will occur.
---
-John
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Rose-db-object mailing list
Rose-db-object@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rose-db-object
