Re: [sqlite] Checking for errors in sqlite3_column_*

but this didn’t. On Thu, 7 Jun 2018 20:14:35 -0700 Christopher Head wrote: > Hello, > I have a question regarding checking for errors that occur when > calling sqlite3_column_*. > > From this manual page: > > https://sqlite.org/c3ref/column_blob.html > > it seems that the

[sqlite] Checking for errors in sqlite3_column_*

with SQLITE_NOMEM (and that’s detectable because sqlite3_step returns a result code as its return value), but that doesn’t seem to be documented anywhere in the manual at all. So what’s the proper way to check for errors in these functions? Thanks! -- Christopher Head pgpTnVwWkaqQ0.pgp

Re: [sqlite] Filename encoding on Unix platforms

seems to suggest that a pathname may not be in any specific character encoding, and, in fact, may not even be a “character string” (i.e. text). It doesn’t mention UTF-8. Anyway, now that I know the plan is not to change SQLite’s behaviour, I’ll treat it accordingly. -- Christopher Head

[sqlite] Filename encoding on Unix platforms

der it a bug) gets fixed? Thanks for the clarification, and please note that I am not subscribed to this list so I would appreciate being included explicitly in replies. -- Christopher Head pgpGC4T9j_U9d.pgp Description: OpenPGP digital signature ___