Re: [sqlite] The need for sqlite3_encode_binary and sqlite3_decode_binary

much thanks. My background is as a very strongly performance-oriented Oracle developer and DBA, and nearly every example I see for using sqlite3 uses non-optimal techniques which either blow through memory allocations, or become subject to SQL-injection attacks. On a related note, what's the

Re: [sqlite] The need for sqlite3_encode_binary and sqlite3_decode_binary

Andrew Finkenstadt wrote: It would appear that by using bind variables instead of '%Q' in the SQL string, the need for sqlite3_encode_binary and sqlite3_decode_binary is eliminated. Is that indeed the case? Andy, Yes that is the case. You can use sqlite3_bind_blob to pass arbitrary binary

[sqlite] The need for sqlite3_encode_binary and sqlite3_decode_binary

It would appear that by using bind variables instead of '%Q' in the SQL string, the need for sqlite3_encode_binary and sqlite3_decode_binary is eliminated. Is that indeed the case? --andy