Hi Mark, > My problem was that I did not find a way to properly reproduce the String > NULL -> "" bug with derby, so I thought it's easier to show the bug in a > small project on it's own.
That's OK. A recent change [1] was committed on trunk. If you please, you can a) verify if I have faithfully reproduced the test scenario b) try that revision for the original unique constraint on null/empty String on a database of your choice. [1] http://openjpa.208410.n2.nabble.com/svn-commit-r941362-in-openjpa-trunk-openjpa-jdbc-src-main-java-org-apache-openjpa-jdbc-schema-openjp-td5009752.html#a5009752 ----- Pinaki -- View this message in context: http://openjpa.208410.n2.nabble.com/Spring-3-0-2-OpenJPA-2-0-Slice-OutOfMemoryError-shortly-after-pounding-1000-threads-to-the-system-tp5000822p5014474.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
