Creating multiple db files with version

[osecen]

We are using this library in one of our services and with the code change to add uuid to tmp files, our service started creating db of the form sqlite-jdbc-tmp-3ca14337-a83f-4281-b8fb-a79f32aa69d0.db continuously and the service runs out of disk space. With this change, the old db is never deleted.
I would like to confirm my thought process and explore ways to remediate this issue.

Thanks,
Onder

[gotson]

The change you refer to does not create the db but copy the dll to a temp dir.

[osecen]

We have a CSV file and a sqlite database of that CSV file in the codebase. During runtime, server uses DriverManager from java.sql to get a Connection to the sqlite db on the server. During that call, since we are using a new filename with uuid, old files are ignored and the sqlite db is copied to a new db in tmp folder. In the old code, since the hashCode was the same, we didn't have this issue.

[gotson]

Can you explain how you load the db? Why do you use :resource: if you have the file locally?

[osecen]

The db file is located in the same jar with the code that is using this driver so it is not in the local file system. What is the proper way of using the db from the jar?
The current call has this format for db jdbc:sqlite::resource:com/myorg/data/mydatabase.db

[gotson]

You should consider extracting yourself to a location you know has enough space.

[frustaci]

I wonder what was the real reason behind the change to use a random uuid since that also left a big part of code as dead code since, if (dbFile.exists()) will always be false, hence not only it will dupe files, the cache wont work.