Absolutely agree; only mention that my request for "a 16 bit version of the
sqlite3_get_table" refers to a UTF-16 version -as usual in the actual C/C++
API-.
Of course, besides -or instead- the requested function, would be great
disclose the SQLite UTF-8/UTF-16 conversion mechanism.
On Tue, Sep 01, 2009 at 10:41:27AM +0200, A.J.Millan wrote:
> * Make sure there was no 16-bit version of the sqlite3_get_table at
> function -perhaps it would be a good idea to include it in the standard API.
> The reason is the same who advised include the current version.
It might be easier
A.J.Millan wrote:
> In fact, actually I'm using the new style querys, and my question was
> an attempt to:
>
> * Make sure there was no 16-bit version of the sqlite3_get_table at
> function -perhaps it would be a good idea to include it in the
> standard API. The reason is the same who advised
Atul, Igor:
Thanks for your kind replies.
In fact, actually I'm using the new style querys, and my question was an
attempt to:
* Make sure there was no 16-bit version of the sqlite3_get_table at
function -perhaps it would be a good idea to include it in the standard API.
The reason is the
A.J.Millan wrote:
>
> Perhaps a seudo-code who let the same result using the standard API
> functions would be enough.
>
> Check this out,It might help
>
> http://www.sqlite.org/cintro.html will help.
>
> Also see http://www.sqlite.org/cvstrac/wiki?p=SimpleCode for example of
> use.
>
5 matches
Mail list logo