-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/27/2010 01:52 PM, Alexey Pechnikov wrote:
> Why difficulty?
I meant supporting any possible pragma, without having to hard code a list
of column names for each one. Implementing your approach and using virtual
tables both require knowing the column names. Example usages:
select pragma_to_table("pragma something or other", "temp.foo");
select * from temp.foo;
or
create virtual table pragma_something("pragma something or other");
select * from pragma_something;
I think it is sufficient to call prepare on the pragma and then column_name
on the prepared statement, but don't know what happens when there are no
results (eg pragma table_info on a non-existent table).
> It's more simple than to discuss about :-)
The underlying issue was not really about the difficulty of making pragmas
behave more like selects (easy to solve), but rather using hostile
development environments that statically wrap up SQLite inside, don't
provide a reasonably complete access to SQLite APIs, and won't update their
wrapping to do so.
If they don't allow you to turn on extension loading then only core changes
to SQLite will (eventually) get through, or the development environment
getting friendlier or the user deciding to use a different environment that
isn't so restrictive and unwilling to change.
Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkxPWRUACgkQmOOfHg372QQ1dQCgiChbyJpBkcUoe3hXIY3H9aEf
AjUAoNyROutO6tG9B3gDpJ8NaWEPlvOM
=roCg
-----END PGP SIGNATURE-----
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
