> Igor Tandetnik wrote on 24/02/2010:
>
> I must admit I have no idea what you are talking about, you lost me
> thoroughly. In any case, mutex or no mutex, the pointer returned by
> sqlite3_column_value is only valid until you step away from that row
> or reset the statement. You can't hold onto
wcl...@gfs-hofheim.de wrote:
> Igor Tandetnik wrote on 24/02/2010:
>
>> Well, too bad.
>
> Ha! Nothing's that bad!!!
>
>> "Protected" means "a mutex is held while the value is outstanding".
>> If such a hypothetical API existed, it would mean you could instruct
>> SQLite to hold a mutex for an
Igor Tandetnik wrote on 24/02/2010:
> Well, too bad.
Ha! Nothing's that bad!!!
> "Protected" means "a mutex is held while the value is outstanding".
> If such a hypothetical API existed, it would mean you could instruct
> SQLite to hold a mutex for an indefinite period of time, thus
>
wcl...@gfs-hofheim.de wrote:
> What I would really like to be able to do would be to cache objects
> returned by sqlite3_column_value(...) and process them later, even after
> the statement that generated them is finalised
You can't. The only thing you can reliably do with the result of
Hi,
I understand from reading http://www.sqlite.org/c3ref/value.html that
there is a distinction between protected and unprotected value objects,
and that some api interfaces, notably sqlite3_value*, require the former
and others, notably sqlite3_column*, provide the latter.
What I would
5 matches
Mail list logo
