Re: [sqlite] convert CString for statement

If you are compiling for Unicode, your CString has a LPCWSTR (const wchar_t*) operator. In that case use sqlite3_bind_text16. If you're not using Unicode, then there is a LPCSTR (const char*) operator that will let you use sqlite3_bind_text directly like Alessandro shows. Doug -Original

Re: [sqlite] I consider this a bug. Anyone else?

Having Debug data isn't a concern for me (but maybe for others?), but not having a version number in SQLite.DLL is a bit of a pain. It means installers can't treat the DLL like every other DLL out there and instead need to rely on file timestamps which is not the greatest. Doug -Original

[sqlite] Extended error code values

The list of extended error codes on http://www.sqlite.org/c3ref/c_abort_rollback.html are in a format that is fairly inconvenient when you're trying to lookup an error value. Below are what they resolve to, and I'm wondering if perhaps someone could update the page to show those values for future

[sqlite] Database full error?

I have a customer with a database whose file size is about 39GB. He's getting error 13 (database or disk is full) on an insert. My app sets the page size to 4096, but even if it was the default, this error shouldn't happen until it's around 4TB in size based on what I read the default