On 23 Sep 2011 at 11:18, Mirek Suk <mira....@centrum.cz> wrote: 

> Dne 23.9.2011 4:41, Igor Tandetnik napsal(a):

>> Note that I didn't say it was wise to store NUL characters as part of the
>> string - I only said that you could do it if you wanted to. sqlite3_bind_text
>> takes the length parameter at face value, and stores exactly as many bytes as
>> you tell it to store. It's up to you to ensure that the values actually make
>> sense for your application. Garbage in/garbage out and all that.

> I just find entire nul handling in SQLite strange. it's C API why not
> expect C (that is nul terminated) strings.

Not in my case it's not. In my case it's the PHP API and I would be very 
annoyed if strings came back with unexpected NULs at the end, or if any NUL I 
insert in the middle of a string acted as a terminator.

--
Cheers  --  Tim
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to