db-torque-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Fischer <fisc...@seitenbau.net>
Subject SV: Column ambiguously defined
Date Thu, 28 Apr 2005 10:39:11 GMT

"Bouvet Konsulent" <bouvetkons@statnett.no> schrieb am 28.04.2005 12:05:37:

> hello again,
> thank you for all your help, it has been very useful.

You are welcome.

> 1. Your diagnoisis was right. Using criteria.setLimit(0); made the
> query work fine
> 2. I tried to do a
> ChannelDocumentLatestPeer.doSelectJoinDocument(crit);
> This did not work very well, however. The generated SQL was exactly
> like the query which generated a 'ORA-00918: column ambiguously
> defined' error.
> I am using Oracle 8.1.7, which does not handle joins very well.
> Keywords like 'inner join' were not introduced before version 9.
> Maybe that has something to do with it? Does Torque generate SQL
> based on the _version_ of the database, by using the corresponding

No, this would also fail within Oracle 10g. It is a problem with the way
oracle handles limit/offset and how it is handled in Torque.

> 3. I ended up doing
> List docs = DocumentPeer.doSelectVillageRecords(crit);
> transfer docs into objects
> building a criteria for ChannelDocumentLatest
> List l = ChannelDocumentLatestPeer.doSelectVillageRecords(cdlCriteria);
> transfer l into object 'latest'
> doc.setOriginatingChannel(latest.getOriginatingChannelId());
> so I ended up with one more SQL-query to get my foreign key to add
> to the Document-object, but I guess that is ok.

I do the same most of the time.

> once more: thank you for your help!
> cheers,
> pj


To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org

View raw message