Just for info, I managed to identify the source of that issue. It is indeed a bug in DataNucleus' SQL generation, and while tracking this one, I even found another one in the same department, even more critical - basically a showstopper.
Thus, I decided to swap out DataNucleus for EclipseLink. After a bit of reworking the code to adapt to the new JPA provider's behaviour, everything works like a charm now. Thanks again for your help, Noel. Cheers, Carsten Am Dienstag, 7. März 2017 19:35:59 UTC+1 schrieb Noel Grandin: > > Either in DataNucleus, or possibly in your code, if you are using some > extension or bypass API possibly. > > There is also an outside chance that H2 is doing something weird like > returning dodgy metadata that is confusing DataNucleus. > > I'm guessing that they are going to ask for a standalone test-case. > > You could try testing with Derby, just to be sure. > > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
