Just out of curiosity, either by including it as another SQLite built in table, or, a user added table after the fact, couldn't a relationship be built between the new table and a comment, or a field in a table and comment be made? So for example (A very VERY loose example)
create table sqlite_comment (identifier char, comment char) or create table sqlite_comment (identifier integer, comment char) Identifier could either be a fully qualified name (IE: tMyTable or tMyTable.UserDetails) and comment could be the required meta data? On Tue, Jun 18, 2013 at 1:05 PM, Klaas V <klaasva...@yahoo.com> wrote: > Dear fellow users and managers of SQLite, > > Alexey Pechnikov wrote: > > >Bad idea. The schema definition can't be modified! > > In fact it's possible if you use the writable schema pragma > http://www.sqlite.org/pragma.html#pragma_writable_schema > > An application could drop all applicable `ls -l` and `id -P`-results in a > database, fire triggers execute one or more smart functions and "presto". > Can be done, me seems. This way not such a bad idea as Alexey thinks. > > As said in the link you have to know well what you're doing, but this is > a good advice always. > > Kind regards, > Klaas `Z4us` V > > _______________________________________________ > 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
