On 3/16/07, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote:
This does look like a bug in MySQL (see http://bugs.mysql.com/bug.php? id=5037 ). Supposedly this is fixed in as of version 5.0.20.
Thanks for looking into this. I'm using 5.0.27-standard, so perhaps that bug is not the problem -- or it wasn't fixed.
In general, we use subselects for bulk operations because delete and update SQL statements do not allow the specification of multiple tables, so only the simplest bulk operations would be possible without the ability to use subselects.
Is it possible to turn off OpenJPA generated sub-selects and only do a sub-select when an application query uses one? That's the default behavior in Toplink/JPA. - Dave
