-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/07/2010 11:57 PM, Andy Gibbs wrote: > But what I wonder is, for what purpose it can be used? On the face of it, > it seems very useful, but then as you read through the description you find > a whole load of statement types that return an "undefined" result
You are indeed correct. It was added and is called by Fossil after using an authorizer. I did (twice) raise these issues with the team before release with no response. http://osdir.com/ml/sqlite-dev/2010-12/msg00002.html It isn't marked as experimental so the semantics can never be changed or improved. Its existence implies something missing in authorizers which is what should have been addressed. And as you observe the undefineds mean it isn't particularly useful anyway. This is the only code that currently uses sqlite3_stmt_readonly: http://www.fossil-scm.org/fossil/fdiff?v1=68a30b40cb6fde3d&v2=6b2674f05c467a3c Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0ATD8ACgkQmOOfHg372QTZUwCgtBt3gY50XsLCA37IeKTG1w/3 rOgAoL6daZt6gaFk9uI8iVJdDxG21Q7e =h/5B -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
