Closed SomaLily closed 1 week ago
Hi SomaLily, I can reproduce the issue. I understand the original fix didn't resolve root cause, which I didn't look into enough to understand in the first place. I agree a fix is necessary.
Hi SomaLily, I've written a fix for this issue by ensuring each thread has their own connection to any sqlite database. The performance overhead is very minimal. Thank you for the test case, I have added it to the test suite. The correction will be in the next thermo release. Sincerely, Caleb
Hi CalebBell, I'm glad to hear that! It would be helpful! I love thermo! Best regards, Soma
Hello, This fix landed in thermo 0.4.0 released today. Sincerely, Caleb
following #140 when 0.3.0 updated,
SQLite objects created in a thread can only be used in that same thread
issue had been done. But similar problem still alive. I changed thetest_unifac_sql_connection_check_threading_false
test method like this:then the
Recursive use of cursors not allowed
issue raises up, which is likely because thermo using a globalUNIFAC_DDBST_ASSIGNMENT_CURSOR
. Wondering if one could change it to local, may avoid this kind of SQLite issue ever ever.