On 6/30/07, Michael Lackhoff <[EMAIL PROTECTED]> wrote:
> The subselect I use, relies on the aliasing of 'gruppen' to 't1'. Of
> course I can just change the definition to use the original table
> name but since I didn't find any mention in the change log, perhaps
> this is a bug?
Tables are only aliased as tN when more than one table is involved in
the query. This "more than one" count does not include literal
subqueries like yours, however. I'm thinking of changing it in 0.765
so that the tN aliases are always used, which would solve your problem
(and many of my own too :)
> All I found was this:
> * Turned off unique column aliases by default and added the
> unique_aliases Manager parameter to turn them back on.
That's something different. It's this:
SELECT
id AS t1_id,
name AS t1_name,
...
The "unique column aliases" are the "tN_<column>" aliases. It is not
related to the tN table aliases.
> Or is there a way to get the same result without a subselect, so that
> the whole SQL is behind the scenes and I don't have to watch out for
> future changes in the generated SQL?
Not yet. Literal subselects are still the only option.
-John
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Rose-db-object mailing list
Rose-db-object@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rose-db-object
