We've found this problem varies from driver to driver. Oracle copes with the
problem. MSSQL and HSQL don't do so well. We've found that OQL strings with
hardcoded values generate more OQL2SQL issues then OQL strings with $1-type
parameters.
Also, try expressing the OQL in different manners, sometimes this has solved
our problems as well.
Ijonas.
----- Original Message -----
From: "Lunar" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 17, 2002 8:42 PM
Subject: Re: [castor-dev] Bug in OQL to SQL translation...?
> "Thomas Yip" <[EMAIL PROTECTED]> wrote :
> > It is called "table alias". Don't have time to explain it.
>
> I'm sorry but if the following exception give me the exact statement that
> was sent, Castor forget aliasing player_0 to player !
>
> > >java.sql.SQLException: Column not found: ID in statement
> > > [SELECT action_queue.id,action_queue.player_id,action_queue.data
> > > FROM player,action_queue
> > > WHERE action_queue.player_id=player_0.id
> > > AND player_0.money = 0]
>
> This should be :
> SELECT action_queue.id,action_queue.player_id,action_queue.data
> FROM player player_0,action_queue
> WHERE action_queue.player_id=player_0.id
> AND player_0.money = 0
>
> Or am I wrong another time ?
>
> Lunar.
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
>
>
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
