 1 | and another dedicated disk only for the recovery file. Using fast SSD disks. Once in a while the recovery |
1 | have change this and cut heap size to 512MB, so database should crash much faster. That was fast |
1 | use. The next guess is that maybe the query is executed fast, but loading the results takes a lot |
1 | Possible issue for JPQL "LEFT [OUTER] JOIN" is doing "[INNER] JOIN". Thanks. Thank you for this report. Please try build 2.3.7_18 that should fix this issue. Great and fast solution but it doesn't work with the following JPQL queries string: - "SELECT a,b FROM A a LEFT OUTER JOIN a.listB b |
1 | performance as explained in the manual. Thank you very much for your professional, super fast support! Highly appreciated! Best, Benjamin lorenz2304 |
1 | your exact test case. Build 2.7.1_09 should fix your test case as well. That did it! Thanks for your fast response. sjzlondon |
1 | you for the fast support, indeed the few classes that were not entity nor embeddable have been set as |
1 | you for fast response. The fix changed the number 51 to 34. But it looks like my db was corrupted |
1 | (not JPA). * Database access needs to be super fast, like microsecond times. * The application |
1 | was forced to work with reasonably low numbers of objects. If this completes too fast on your machines, try |