Hi Frank,
As I explained in one of my earlier emails, tests that require a database will
not be added to jtreg. I have a unit test suite which i use for that but that
is not external
Best
Lance
On Dec 10, 2012, at 2:44 AM, Frank Ding wrote:
Hi Lance,
The code refactory looks good. By
Hi Lance,
The code refactory looks good. By the way, the newly added unit test
is not jtreg test case?
Best regards,
Frank
On 12/5/2012 4:38 AM, Lance Andersen - Oracle wrote:
All,
Attached is the patch for: 8004374 based off the issue that Frank
reported.
for
Hi Lance,
Thanks for your clarification. I created the test case you requested
and attached it in this email. Please review it. By the way, the new
Oracle bug (internal id 2376620) submitted by me several days ago seems
not having been reviewed. Could you also help me on this?
Best
I will get to it sometime within the next week. Have some higher priority
items to address first
Best
Lance
On Dec 3, 2012, at 3:17 AM, Frank Ding wrote:
Hi Lance,
Thanks for your clarification. I created the test case you requested and
attached it in this email. Please review it. By
Hi Frank,
Thank you for the note
If you could in the future, please provide a complete test program to repro
the issue as it would save time with the reviews. Ideally if the issue is not
database specific it would be good to leverage Java DB as it is included within
Oracle JDK
I will
Hi Lance
Thanks for your quick response. Please find the bug info below.
The problem:
When CachedRowSetImpl.acceptChanges() is called, incorrect number of
conflicts, if any, is reported. The number of conflicts is the actual
number of existing rows in database, which is the size of
Frank,
If you can please post the bug info here, I will take a look at your patch
Best
Lance
On Nov 8, 2012, at 10:01 PM, Frank Ding wrote:
Hi guys,
We discovered a bug in CachedRowSetWriter.writeData method where incorrect
number of conflicts is reported. I searched in Oracle bug
