I have not observed the problem as documented by the original reporter. The last scenario Andrei suggested fails (using Oracle) on both 2.5.0 and 2.5.1 — where 2.5.1 is supposed to be fixed, so clearly the unit test does not reproduce the original problem yet. It makes absolutely no sense to even try run with DB2 if I can’t reproduce the original problem using Oracle.
Once I have a test that: 1) Reproduces the problem (unit test fails) using ECL 2.5.0 using Oracle AND 2) (unit test) Passes when using ECL 2.5.1 (which the fix was integrated into) using Oracle
Then I can give it a run against DB2. Until those criteria are satisfied I am blocked.
Hi Rick,
both me and Andrei do not have access to DB2 and we are quite busy
at this moment. But looks like J Grassel already saw this problem on
Oracle DB (as Andrei told me).
Think he can try the same with DB2 to see if it works fine or not.
If he still won't be able to reproduce it, I'll push this back on
our side and I'll ask to come back with working test-case.
Tomas
Dne 9/9/14, 5:01 PM, Rick Curtis
napsal(a):
Andrei, Tomas -
By any chance can you guys come up with a proper
EclipseLink test(or even standalone) that reproduces the
failure? Lots of time has been spent on our end trying to
reproduce this problem to no avail. Also, shouldn't we be
adding a test with the bug fix in 295556?
Thanks,
RIck
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
_______________________________________________ eclipselink-dev mailing list eclipselink-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/eclipselink-dev |