Topic: q about alwaysUseColumnAlias

by imario 17 Mar 12:47

q about alwaysUseColumnAlias

Hi!

I've seen you change the column alias stuff a little bit.

With this change (according to the documentation) you are now going to alias only key columns of an associated entity.

But what happens if a normal column do have the same name? Then, the "duplicate column name" problem is back again.
In fact, I do have it again :-) Happily I am able to set alwaysUseColumnAlias to true!

My gut feeling is, that Avaje should use alwaysUseColumnAlias=true by default, or at least as soon as a joined table comes into play.

Hmmm ... Just my opinion :-)

Ciao,
Mario

17 Mar 21:03

by Rob

> But what happens if a normal column do have the same name?
All the columns have a table alias... so this is only an issue if the same column on the same table appears twice.

So I'm interested to know how/why this happens?

Thanks, Rob.

18 Mar 07:04

by imario

Hmmm ....

But the select looks like

select m.prop1, m.prop2, a.prop1, a.prop2 from ....

This makes the database fail as the name prop1 is not unique.

I'll try to create a test-case.

Ciao,
Mario

Create a New Topic

Title:
Body:	$paramtool.getParamIfNull('nt_body','')

Add Comment

Create a New Topic