gwenn

Sorry but I don't know how to cross compile `libsqlite3-sys`.

Not ready ? ``` error: Miri evaluation error: can't call foreign function: sqlite3_threadsafe --> src/inner_connection.rs:372:17 | 372 | if unsafe { ffi::sqlite3_threadsafe() == 0 } { | ^^^^^^^^^^^^^^^^^^^^^^^^^ Miri evaluation...

It seems unsustainable to introduce new features / new bindgens each time. I would prefer keeping only the `modern_sqlite` feature. And you can now use [alloc](https://github.com/jgallagher/rusqlite/pull/644) instead of `CString` +...

https://github.com/jgallagher/rusqlite/issues/293#issuecomment-326995795

@thomcc I don't know. No trace of `SQLITE_CORE` nor `SQLITE_ENABLE_STAT2 ` in: * `PRAGMA compile_options;` output with sqlite3 client on Arch linux. * [apsw](https://github.com/rogerbinns/apsw/blob/master/setup.py#L583) * [go-sqlite3](https://github.com/mattn/go-sqlite3/blob/master/sqlite3.go#L13-L21) * [javasqlite](https://www.sqlite.org/java/dir?ci=tip) `SQLITE_CORE` is...

[sqlite3_trace_v2](http://sqlite.org/c3ref/trace_v2.html), available since 2017-03-30 (3.18.0), makes possible to pass a custom `pCtx`. But `pCtx` lifetime is not handled by SQLite...

Could you please be more specific ? For example, you cannot reasonably transform an `HH:MM` into a `OffsetDateTime` ! And I don't expect `now` to be stored in an SQLite...

https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=96658251e57771ee6b87252637f1a22d => It seems not possible to parse offset '+HH:MM' with '%z' but `Rfc3339` can ! https://github.com/time-rs/time/issues/241 ```rust let input = "2013-10-07 04:23:19.120-04:00"; let result = PrimitiveDateTime::parse(input, "%Y-%m-%d %H:%M:%S.%N"); println!("{:?}",...

https://github.com/time-rs/time/issues/329

Could you please do the same with optional offset / timezone [+-]HH:MM" ? Or maybe we should drop support to `OffsetDateTime` (and support only `PrimitiveDateTime`) ?