On 09/09/11 12:31, Stephan Beal wrote:
Maybe this is a bug, maybe not, but i've certainly never seen it before...
i'm intentionally introducing SQL errors to test my JSON-side error
handling, and i found that this:
rc = sqlite3_prepare_v2(g.db, zSql, -1, pStmt-pStmt, 0);
outputs to stderr
On 09/09/11 12:34, Martin S. Weber wrote:
Really? I'm assuming the JSON output goes to stdout, and the error message
goes to stderr. In that case it wouldn't interfere with the JSON output at
all. Just pipe the output to your json reader without a 21...there'll be no
problem.
That being said,
On Fri, Sep 9, 2011 at 6:35 PM, Martin S. Weber martin.we...@nist.govwrote:
That being said, of course a library should never write to stderr directly.
i just found the reason for it:
/* Error logs from SQLite */
void fossil_sqlite_log(void *notUsed, int iCode, const char *zErrmsg){
3 matches
Mail list logo