Re: [sqlite] Using SQLite internal recognizers eg: SQLITE_PRIVATE int sqlite3AtoF()

I am drawing from parallel functionality in the existing API.Roughly, the API sqlite3_buffer_numeric_type() would simply be the buffer input version of the existing API sqlite3_value_numeric_type(). But instead of operating on a sqlite3_value parameter, it would read from a pzBuffer parameter

Re: [sqlite] Using SQLite internal recognizers eg: SQLITE_PRIVATE int sqlite3AtoF()

On 1/23/18, petern wrote: > Any chance of publishing a modest but hardened "int > sqlite3_numeric_buffer_type(const char*pBuffer,int length,int encoding)" > API that extensions can use? I'm not sure what "sqlite3_numeric_buffer_type()" is suppose to do? -- D.

Re: [sqlite] Using SQLite internal recognizers eg: SQLITE_PRIVATE int sqlite3AtoF()

Any chance of publishing a modest but hardened "int sqlite3_numeric_buffer_type(const char*pBuffer,int length,int encoding)" API that extensions can use? On Tue, Jan 23, 2018 at 4:43 PM, Richard Hipp wrote: > On 1/23/18, petern wrote: > > What is

Re: [sqlite] Using SQLite internal recognizers eg: SQLITE_PRIVATE int sqlite3AtoF()

On 1/23/18, petern wrote: > What is the fastest forward compatible way to gain use of the internal > buffer value recognizers such as "SQLITE_PRIVATE int sqlite3AtoF()" in > external C programs? > There is no forwards-compatible way to do that. We reserve the right

[sqlite] Using SQLite internal recognizers eg: SQLITE_PRIVATE int sqlite3AtoF()

What is the fastest forward compatible way to gain use of the internal buffer value recognizers such as "SQLITE_PRIVATE int sqlite3AtoF()" in external C programs? The goal is to efficiently compute exactly how SQLite would taxonomically classify {numeric,float,integer,...} a buffer string value