Rick Hillegas-3 wrote:
>
>
> This means that more than 1 row is returned by the subquery. That, in
> turn, suggests that the query, which succeeds for you on another
> database, may not be behaving in a predictable way there. Since more
> than one row qualifies to drive the update, which row do you want? Is
> there some other restriction which you can put in the subquery to
> guarantee that you get one, predictable row?
>
> Hope this helps,
> -Rick
>
>
I wonder why this doesn't cause a problem for Access?
--
View this message in context:
http://old.nabble.com/Porting-to-standard-SQL-tp33253800p33273439.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
