On 10/10/05 9:16 AM, Uwe Voelker wrote:
>> Did you try it? :) I already do expansion (and sometimes compression to tN
>> aliases) within sort_by strings.
>
> Yes. "sort_by => 'id'" did not work, error came from DBI, was "ORDER BY
> id" - so no expansion at all.
> (All three tables had the 'id' co
Did you try it? :) I already do expansion (and sometimes compression to tN
aliases) within sort_by strings.
Yes. "sort_by => 'id'" did not work, error came from DBI, was "ORDER BY
id" - so no expansion at all.
(All three tables had the 'id' column.)
DBD::mysql::st execute failed: Column: 'id
On 10/10/05 5:41 AM, Uwe Voelker wrote:
> Cool. Now only 'sort_by' is missing. What about this:
> 1. if it's a scalar, use it as it is (use as sql snippet)
> 2. if it's a arrayref expand the column as for the 'query' parameter
Did you try it? :) I already do expansion (and sometimes compression t
Hello John,
What about this rule:
1. if a column is not prefixed, it is the main object.
2. every other column has to be prefixed with the relationship name
I already did this and checked it in. You can still use the "tN" table
names and "tN_" column prefixes if you want, but if not, then jus
On 10/9/05 1:09 PM, Uwe Voelker wrote:
> What about this rule:
> 1. if a column is not prefixed, it is the main object.
> 2. every other column has to be prefixed with the relationship name
I already did this and checked it in. You can still use the "tN" table
names and "tN_" column prefixes if y
Hello John,
Adding support for relationship names actually introduces ambiguity here.
Now when faced with a prefix, it could be a table alias, a table name, or a
relationship name, all of which can overlap. While I think this won't be
too bad in the limited scope of the "distinct" param, I worr
On 10/7/05 10:30 AM, Uwe Voelker wrote:
> 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
On 10/7/05 10:30 AM, Uwe Voelker wrote:
>> 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.
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...
ARRAYRE
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
If set to any kind of true value, then the "DISTINCT" SQL k
10 matches
Mail list logo
