> -Original Message-
> Behalf Of J Decker
...
> wrote:
>
> > Dave. The documentation contains many such catch-all
> statements which do
...
> > The current decision tree of the particular catch-all
> documentation comment
...
> > int
On Wed, Dec 13, 2017 at 1:25 PM, petern wrote:
> Dave. The documentation contains many such catch-all statements which do
> not reflect a full decision tree. The usual cover story will either be (I
> paraphrase) : 1. "that's an implementation detail" or 2. "it might
Dave. The documentation contains many such catch-all statements which do
not reflect a full decision tree. The usual cover story will either be (I
paraphrase) : 1. "that's an implementation detail" or 2. "it might change
later, so the documentation can only make a short blanket statement".
It is
dave wrote:
> "... the pointer returned from sqlite3_value_blob(), .. can be invalidated
> by a subsequent call to sqlite3_value_bytes(), ..."
> Is that statement still true?
The returned pointer is invalidated when you call a function that forces
SQLite to convert the value into another type.
I have a question regarding the API documention at
http://sqlite.org/c3ref/value_blob.html, which states:
"... the pointer returned from sqlite3_value_blob(), .. can be invalidated
by a subsequent call to sqlite3_value_bytes(), ..."
Is that statement still true? I ask because I notice that the
5 matches
Mail list logo