Dears,

(Writing from mobile, hope the HTML like formatting, which I can't seem to 
override, won't be a total mess in this post).

Have not even yet got to the code to test it and review the new C API but I 
already have a question about:
Added two new C-language interfaces: sqlite3_expanded_sql() 
andsqlite3_trace_v2().
Assuming some blobs are among the parameters will this function 
sqlite3_expanded_sql() try to build a full string representation of it?

This API is *much* welcome for interfaces between applications and SQLite C 
API, when reporting situations rise up, but I fear it could be of less use if 
every statement concerned by blobs will trigger the building of a possibly huge 
string, set to fail for memory allocation reasons (SQLITE_LIMIT_LENGTH or 
others).

I will test it and read its implementation to see by myself as soon as 
possible, though I hope blobs can get a specific treatment, possibly using some 
token to say "here is a blob of length N", instead of returning the whole blob.

Some 'flags' second parameter to the API might offer one flag for selecting the 
output behavior about blobs?... It might be nice to get blobs smaller than N 
bytes to be X'string' represented, and get a placeholder for larger ones.

Kudos for the content of the 'pi' release!

About documentation, is the sessions extension among the targets for the 
documentation effort regarding 3.14 ?

-- 
Meilleures salutations, Met vriendelijke groeten,  Best Regards,
Olivier Mascia (from mobile device), integral.be/om


> Le 23 juil. 2016 à 17:16, Richard Hipp <d...@sqlite.org> a écrit :
> 
> The next release of SQLite will be the "pi" release - version 3.14.
> It will probably occur within the next two weeks.
> 
> Draft change log:  https://www.sqlite.org/draft/releaselog/3_14_0.html
> 
> Code snapshot: 
> https://www.sqlite.org/snapshot/sqlite-snapshot-201607230522.tar.gz
> 
> Testing and (especially) documentation work is on-going.  Please try
> out the snapshot.  Look over the changes.  Speak up loudly and quickly
> if you have any issues.  If you do not want to post to this mailing
> list, you can send feedback directly to my email address shown below.
> 
> Thanks.
> 
> -- 
> D. Richard Hipp
> d...@sqlite.org
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to