if I only had a unit test... sigh... the lack of a proper test is probably the reason why
the failure was reintroduced in 3.3.0.
I'm pretty convinced this issue only shows on certain dbs, such as Oracle and
Postgres. I can give it another try on MySQL, too (and then write a proper test ;-) )
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4196980#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...