Is this a bug in derby? Is there a workaround? I'm running Derby 10.1.2.1 on Fedora Core 5.
I don't have an explanation for the behavior you are seeing. I spent a little bit of time trying to reproduce your problem with a smaller query, but couldn't.
Can you post a complete example script, with full DDL for the tables, that demonstrates the problem? thanks, bryan
