gwenn

> @gwenn the reason for using `get_raw` is that you might want to avoid copying the `&str` to a `String`. Ok, but you cannot avoid returning an owned (sub)String from...

You mean https://github.com/rusqlite/rusqlite/blob/master/src/error.rs#L184-L204 does not work ?

https://github.com/rusqlite/rusqlite/pull/838/files#diff-b1a35a68f14e696205874893c07fd24fdb88882b47c23cc0e0c80a30c7d53759R1626 So `get_raw` is not so painful to use...

Could you please confirm that reverting https://github.com/jgallagher/rusqlite/commit/9f009fe1e03c7c428305e88dc5e2269c69c421cf fixes the problem ?

This PR partially rollbacks #961 related to cross-compilation...

> I see. According to [the `target_env` docs](https://doc.rust-lang.org/reference/conditional-compilation.html#target_env): > > > For historical reasons, this value is only defined as not the empty-string when actually needed for disambiguation. > >...

https://www.mail-archive.com/[email protected]/msg100570.html >> Does a registered sqlite3_update_hook get called when _any_ SQLite connection >> modifies the database (not just the connection it's registered with)? > No, only the connection it's registered...

As a quick fix, I added a symbolic link to rusqlite README but a dedicated README would be better...

Sorry, I don't know ! We should also report this issue to [sqlx](https://github.com/launchbadge/sqlx/blob/3b503a7764c49d17cc166f81536c669a19248102/sqlx-core/src/sqlite/connection/collation.rs#L59)...

And there is another issue ! https://sqlite.org/c3ref/create_collation.html > The xDestroy callback is not called if the sqlite3_create_collation_v2() function fails. Applications that invoke sqlite3_create_collation_v2() with a non-NULL xDestroy argument should check...