You could make a extra table that has a foreign key on sqlite_master and add extra attributes... You could add comments ( -- ) in the create statemtents; and parse those back out ...
On Fri, Apr 20, 2018 at 3:52 PM, Randall Smith <rsm...@qti.qualcomm.com> wrote: > I'm writing some code to do processing of some (but not quite all) of the > tables in my SQLite database. I could make this a lot easier and more > general purpose if I could somehow attach an attribute to the various > tables that indicated whether that table should be processed. > > Other than, say, keying off something in the table name or something which > is a pain because all the table names are already set in stone, is there > any way good of doing this? I was hoping there was something in, say, the > sqlite_master table I could intentionally affect and then use later. But > nothing jumps out. Maybe define some kind of bogus index for the table I > could check for? But I'm hoping there's something with more grace and > beauty. > > Thanks for any ideas or suggestions. > > Randall. > > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
