Ok,
Thanks.
On Tue, Jun 3, 2014 at 8:42 PM, Richard Hipp wrote:
> On Tue, Jun 3, 2014 at 2:27 PM, gwenn wrote:
>
>> Hello,
>> The function "sqlite3_stmt_readonly" returns true/1 for the statement
>> "DROP TABLE IF EXISTS test" when the table "test" does not exist.
>> But, if this drop statement is cached, "sqlite3_stmt_readonly" still
>> returns true even after creating the table "test".
>> The only way I've found to make "sqlite3_stmt_readonly" returns false
>> is to execute/step the drop statement.
>> Do you know another way to make SQLite "reevaluate" the readonly status ?
>>
>
> Thank you for the bug report.
>
> Because this is a very minor issue and because we are well into the test
> cycle for version 3.8.5 already, we are going to defer looking into this
> problem until after the 3.8.5 release.
>
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
