Version 2.4.0 #318
cljoly
announced in
Announcements
Replies: 2 comments 1 reply
-
|
@LucasPickering I ended up implementing the cache feature, it was easier than expected. Please feel free to test and report here :) |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
@cljoly Yep works for me, thanks so much! EDIT: I should note though that I don't have any migrations that insert rows, they're purely schematic, so I don't think they actually test foreign key checks at all. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Dependencies
Rusqlite was updated from 0.37.0 to 0.38.0.
Please see the release notes for 0.38.0, there are a few breaking changes in this one.
Update other deps dependencies, see git history for details.
Features
Rusqlite 0.38 makes the cache statement optional. This feature was used for foreign key checks. The
rusqlite_migrationlibrary does not enable any features from rusqlite, not even the default one. This way, downstream users can freely chose which feature to enable based on their needs. As a result,rusqlite_migrationnow handles statement caching for foreign key checks internally now. As side benefit, this also makes caching more efficient: the prepared statement is kept for the minimum time where it is needed and freed immediately, without taking space in the global cache used by rusqlite.Other
Dislayof errors is meant for human consuption and not for flow control in the program.What's Changed
Full Changelog: v2.3.0...v2.4.0
This discussion was created from the release Version 2.4.0.
Beta Was this translation helpful? Give feedback.
All reactions