On 29 Aug 2015, at 9:38pm, Darren Duncan <darren at darrenduncan.net> wrote:
> On 2015-08-29 10:41 AM, Domingo Alvarez Duarte wrote: >> It would be nice to have something like this on sqlite too ! >> >> http://blog.aquameta.com/2015/08/29/intro-meta/ I would prefer a system conforming to the information schema part of SQL-92: <https://en.wikipedia.org/wiki/Information_schema> > I won't argue that it is right for SQLite specifically, but I do agree with > the broad principle in general, being able to do all catalog/code > manipulation as data, or homoiconicity. In fact this is a central pillar of > my own Muldis D project, an industrial strength programming language with > fully integrated database functionality. I seem to remember that someone did this for SQLite using VIRTUAL TABLEs. The code took the results of various information pragmas and presented it when you selected on a table of tables, one of indexes, one of triggers, etc.. Someone else wrote some code which performed various queries and created real TABLEs with the appropriate data in. You just called this code when you needed the tables up-to-date. Neither fully implemented the ability to make changes to these virtual tables using triggers. I think some of the manipulations which could be described by UPDATE would be very difficult to implement. Simon.
