On Dec 8, 2010, at 8:44 PM, Richard Hipp wrote: > Now that foreign key constraints are enforced natively, why would you want > to have a list of them?
To know what they are. In the same way as there are pragma that list database, table, column, index, etc... To paraphrase: "Now that tables are implemented natively, why would you want to have a list of them?" To know what they are. These are the building blocks of a data dictionary. Data dictionaries allows introspection. Introspection allows dynamic programming. Case in point, one can pretty much build a useful information schema out of SQLite patchwork of pragmas: http://dev.alt.textdrive.com/browser/IMDB/Info.ddl Out of such information schema, one can build a full ETL (extract, process, load): http://dev.alt.textdrive.com/browser/IMDB/ETL.ddl Why would you want to prevent that? > Why should the foreign_key_list pragma continue to > consume code space and developer maintenance time? Because this is useful information. Such information is added value, not some whimsical luxury. There is a trove of self describing information in the DDL that you seem to purposefully want to keep out of reach. Please reconsider. Thanks in advance. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
