ISAR/rusqlite
3
0
Fork 0
mirror of https://github.com/isar/rusqlite.git synced 2025-04-15 12:57:44 +08:00
Code Issues Packages Projects Releases Wiki Activity

Prepare next release

Browse Source
This commit is contained in:
gwenn 2025-01-19 14:46:14 +01:00
parent a1605d92c3
commit 3dc73601e9
4 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Cargo.toml
View File

@ -1,7 +1,7 @@
[package]
name = "rusqlite"
# Note: Update version in README.md when you change this.
version = "0.32.1"
version = "0.33.0"
authors = ["The rusqlite developers"]
edition = "2021"
description = "Ergonomic wrapper for SQLite"
@ -136,7 +136,7 @@ fallible-iterator = "0.3"
fallible-streaming-iterator = "0.1"
uuid = { version = "1.0", optional = true }
smallvec = "1.6.1"
rusqlite-macros = { path = "rusqlite-macros", version = "0.3.0", optional = true }
rusqlite-macros = { path = "rusqlite-macros", version = "0.4.0", optional = true }
[dev-dependencies]
doc-comment = "0.3"
@ -152,7 +152,7 @@ bencher = "0.1"
[dependencies.libsqlite3-sys]
path = "libsqlite3-sys"
version = "0.30.1"
version = "0.31.0"
[[test]]
name = "auto_ext"

8
README.md
View File

@ -27,7 +27,7 @@ In your Cargo.toml:
# That said, it's not ideal for all scenarios and in particular, generic
# libraries built around `rusqlite` should probably not enable it, which
# is why it is not a default feature -- it could become hard to disable.
rusqlite = { version = "0.32.0", features = ["bundled"] }
rusqlite = { version = "0.33.0", features = ["bundled"] }
```
Simple example usage:
@ -148,11 +148,11 @@ You can adjust this behavior in a number of ways:
* If you use the `bundled`, `bundled-sqlcipher`, or `bundled-sqlcipher-vendored-openssl` features, `libsqlite3-sys` will use the
[cc](https://crates.io/crates/cc) crate to compile SQLite or SQLCipher from source and
link against that. This source is embedded in the `libsqlite3-sys` crate and
is currently SQLite 3.46.0 (as of `rusqlite` 0.32.0 / `libsqlite3-sys`
0.30.0). This is probably the simplest solution to any build problems. You can enable this by adding the following in your `Cargo.toml` file:
is currently SQLite 3.48.0 (as of `rusqlite` 0.33.0 / `libsqlite3-sys`
0.31.0). This is probably the simplest solution to any build problems. You can enable this by adding the following in your `Cargo.toml` file:
```toml
[dependencies.rusqlite]
version = "0.32.0"
version = "0.33.0"
features = ["bundled"]
```
* When using any of the `bundled` features, the build script will honor `SQLITE_MAX_VARIABLE_NUMBER` and `SQLITE_MAX_EXPR_DEPTH` variables. It will also honor a `LIBSQLITE3_FLAGS` variable, which can have a format like `"-USQLITE_ALPHA -DSQLITE_BETA SQLITE_GAMMA ..."`. That would disable the `SQLITE_ALPHA` flag, and set the `SQLITE_BETA` and `SQLITE_GAMMA` flags. (The initial `-D` can be omitted, as on the last one.)

2
libsqlite3-sys/Cargo.toml
View File

@ -1,6 +1,6 @@
[package]
name = "libsqlite3-sys"
version = "0.30.1"
version = "0.31.0"
authors = ["The rusqlite developers"]
edition = "2021"
repository = "https://github.com/rusqlite/rusqlite"

4
rusqlite-macros/Cargo.toml
View File

@ -1,6 +1,6 @@
[package]
name = "rusqlite-macros"
version = "0.3.0"
version = "0.4.0"
authors = ["The rusqlite developers"]
edition = "2021"
description = "Private implementation detail of rusqlite crate"
@ -12,6 +12,6 @@ categories = ["database"]
proc-macro = true
[dependencies]
sqlite3-parser = { version = "0.13", default-features = false, features = ["YYNOERRORRECOVERY"] }
sqlite3-parser = { version = "0.14", default-features = false, features = ["YYNOERRORRECOVERY"] }
fallible-iterator = "0.3"
litrs = { version = "0.4", default-features = false }