-
Bug
-
Resolution: Won't Fix
-
P2
-
None
-
1.4.2_06
-
None
-
x86
-
windows_2000
Using connection pools a set of connections are initialised and later some of the connections insert/update DB (MS Access) and commit, other connections are not returning updated value if they are initialised before update/insert.
Please see attached testcase.
In the testcase, ConnectionA inserts data to TABLE_B and after that
connectionB is initialised.
Then ConnectionB returns 1 row from TABLE_B (which is expected)
If we try inserting one more row. (that is after initialising ConnectionB)
& retrieve data from TABLE_B using connectionB, then it will return only 1 row. (where 2 is expected)
Please unzip the attachment into a folder and run it using startTest.bat
Use the attached TestDatabase.mdb instead of that in zip file since the attached one contains table structure also.
###@###.### 10/18/04 12:54 GMT
Please see attached testcase.
In the testcase, ConnectionA inserts data to TABLE_B and after that
connectionB is initialised.
Then ConnectionB returns 1 row from TABLE_B (which is expected)
If we try inserting one more row. (that is after initialising ConnectionB)
& retrieve data from TABLE_B using connectionB, then it will return only 1 row. (where 2 is expected)
Please unzip the attachment into a folder and run it using startTest.bat
Use the attached TestDatabase.mdb instead of that in zip file since the attached one contains table structure also.
###@###.### 10/18/04 12:54 GMT