It shouldn't be a requirement, as the problem mentionned here : http://db.apache.org/torque/criteria-howto.html ("Using Criterion to use a Column twice in a Criteria") is obviously not what you are encountering : you may have two identical "columnname", but internally, the Torque Runtime is supposed to expand these "columnname" to "tablename.columnname".Hi Thomas,
In addition, where is the home of the village project?
http://wiki.apache.org/db-torque/FrequentlyAskedQuestions
I admit, it was the obvious again. A workaround for my problem certainly is to have unique column names in the whole data model, what means some work for us.
You might however resolve the problem using aliases, just as you would do in raw SQL.
Indeed it seems to be a bug in village (or at least not a feature) that the same column name twice leads to wrong results.
Thank you anyway,
Daniel
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
