5 ms·
(Read the link above properly) "The application is responsible for destroying any objects it allocates" ...smells like user error to me. e.g. "the applicatio
by TickleSteve 10y ago
(Read the link above properly)
"The application is responsible for destroying any objects it allocates"
...smells like user error to me.
e.g. "the application must use sqlite3_finalize() on every prepared statement and sqlite3_close() on every database connection
"
I suggest that if you want to continue to assert that SQLite is not robust, you have to show us your code.
- mSparks 10y agoSo aside from calling finalize how are we supposed to destroy them? Because the number of cases where finalize doesn't destroy them or calling finalize on a closed prepared statement (supposed to be a harmless noop) crashing it completely seems fairly common. Yum is open source. A big chunk of the sqlite tests are not. With plenty of examples of yum sqlite databases becoming corrupt and needing to be rebuilt from scratch why would you need my code. Yum is infinately more important to those millions of users than anything I write. So yeah, great when it works, but testing nothing to be proud of is definitely my experience. Pay for this: TH3 is free to SQLite Consortium members and is available by license to others. No chance. That default encryption is locked behind walls doesn't inspire cooperation either.