-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/12/2010 10:04 AM, Petite Abeille wrote: > Thanks for that. Since 2006? High priority indeed :)
That the ticket averages a small number of comments per year is an indication that perhaps its priority is about right. Many other ticket tracking systems do have voting features so at least people can chime in with 'me toos'. > That said, maybe SQLite has reached a point where it would benefit from a > proper data dictionary of sort, Note that is unrelated to your original issue. No matter how fancy a data dictionary there is, it won't affect getting the name of a failed constraint out. (The technical reason is that under the hood all the constraints are anded together so detecting which one failed would require re-running each one separately.) > But altogether, nothing really comprehensive, nor very accessible (i.e. > multitude of non queryable pragmas or raw DDL). > > Has anyone attempted to outfit SQLite with a proper data dictionary? Your definition of "proper" appears to be some ISO standard :-) SQLite's approach is certainly acceptable to most (evidence: if not there would be a lot of requests for improvement). Also remember that SQLite is not used on a server with lots of different databases, hundreds of tables each, potentially huge numbers of users, dedicated paid support staff etc. But again SQLite does provide the functionality if you want to implement this yourself. For example you can implement a set of virtual tables. This is very easy to do: plug - my Python wrapper: http://apidoc.apsw.googlecode.com/hg/vtable.html Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzdkvAACgkQmOOfHg372QQaxACgn7VBLSOxYc9mtKAeHnuWIrIU hT8AoK8GZ8AsAili0R52OFl+opaPe2pW =ugAe -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users