Jan-Henrik Haukeland wrote:
Yes, the mysql bug is very bad, and a workaround *must* be found. I'll look into that.
I hope we can figure this one out. It's my only real showstopper since my code is now stabile for sqlite and postgres.
sqlite3_prepare_v2() was first added in SQLite version 3.3.9 and libzdb should work with 3.x. But you are right, using this interface, if available, is preferable with regards to error reporting. I'll use an #ifdef to add it.
Please do. I did a small change against libzdb today and tested my code with the v2 interface. A two line change and no more undescriptive errors - just table lock issues under high concurrencies. And those are pretty much unavoidable I guess, unless I set initialConnections/maxConnections both at one. But then throughput is terrible. So I'll take my chances with the table locks and suck up the errors.