You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm the maintainer of JobRunr, an open-source distributed background processing framework for Java.
We try to support all major databases and connection pooling framework, including Sqlite and c3p0. We do encounter a bug when combining c3p0 with Sqlite in our tests: for each test, we drop all tables and recreate them to have a blank slate.
When doing so, the dropping of the table succeeds but when we try to recreate the table, it fails complaining that the table is still there. Any idea why this is and what goes wrong?
Is the work transactional? You might be missing an explicit commit. c3p0 rollsback uncommitted work by default, but that behavior is undefined, perhaps others autocommit?
Dear,
I'm the maintainer of JobRunr, an open-source distributed background processing framework for Java.
We try to support all major databases and connection pooling framework, including Sqlite and c3p0. We do encounter a bug when combining c3p0 with Sqlite in our tests: for each test, we drop all tables and recreate them to have a blank slate.
When doing so, the dropping of the table succeeds but when we try to recreate the table, it fails complaining that the table is still there. Any idea why this is and what goes wrong?
All code is available in our GitHub repo: https://github.com/jobrunr/jobrunr.
The test in question is: C3p0SqLiteStorageProviderTest
Attached the exception log:
The text was updated successfully, but these errors were encountered: