>>>>> Pavel Ivanov writes:
>>>>> On Wed, Oct 12, 2011 at 11:12 AM, Ivan Shmakov wrote:
[…]
>> Consider, e. g.:
>> sqlite3_value *a
>> = sqlite3_int64_value (1);
>> assert (a != 0);
>> sqlite3_value *b
>> = sqlite3_text_value (-1, "qux");
>> sqlite3_value *c
>> = sqlite3_blob_value (blob_size, blob);
>> assert (b != 0);
>> int r;
>> r = db_triv_exec_bound (db, sql_1, a, b, 0);
>> assert (r == SQLITE_OK);
[…]
> You can do absolutely the same thing but use your_own_value* instead
> of sqlite3_value*. Why stick with SQLite's internal data structures?
No special reason, but it would have saved me some work. Not to
mention that it seems to me a bit like a duplicate effort.
Note also that such a code would've to be updated should a new
type be introduced to SQLite (however unlikely, it still may
happen.)
--
FSF associate member #7257
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
