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.
Good. Unfortunately I have no time to test this before the weekend. But
if the release can wait until Monday...
ARRAYREF should be a reference to an array of table names or "tN" table
aliases.
Btw. this morning I had the following idea:
Allow the name of the relation too. For the pod example this would be
'prices' because: Product---(prices)-->Price. (Unfortunately the Price
table is 'prices' too, so this is a bad example.) But by allowing this
the user could completely leave out the table name or the t2, t3 alias.
The same string is used by 'with_objects' and 'require_objects'.
The table aliases tN can get tricky if the query has varying sub-objects
depending on form parameters (or something else). Then I have to use
table names, which I would like to avoid.
And now for "query":
Instead of table alias or table name also allow the above 'relation
name' (or the class name too - I'm not quite sure if this is allowed
now). If no prefix is given, use 't1' (main object), all other columns
need to be prefixed.
In my case I often have to write 't1.xxx => 0' where the above would
allow 'xxx => 0'. Let's assume every participating class/table has the
xxx column.
Bye, Uwe
-------------------------------------------------------
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
