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 best way to give back changes to CppSQLite3DB, one of the myriad C++ front-ends to sqlite3 ? I'm positive I can dedicate the changes to the public domain anywhere except in Germany, in which case I'd be happy assigning them to drh's entity of choice. --andy On 5/10/07, Dennis Cote <[EMAIL PROTECTED]> wrote:
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 data to an SQL statement without worrying about special quoting. Dennis Cote ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
