I think what is being looked for here is information available from many commercial databases. There are elaborate "System" tables containing the entire database structure down to the finest detail including table formats, relationships, triggers, stored procedures, and etc. These tables are standard data tables, but normally protected from everyone but the DBA.
I have not looked at the internals of SQLite, but I believe any schema like query results are created "on the fly" and only persist for the life of the query. Fred > -----Original Message----- > From: Will Leshner [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 25, 2004 11:08 AM > To: [EMAIL PROTECTED] > Subject: Re: [sqlite] Dumping and importing database via Perl > DBD::SQLite > > > Puneet Kishor wrote: > > > One possible way to make this easier > > would be to actually have an alternate "schema table" with such > > information in it for every table. That way one would query _that_ > > alternate "schema table," and instead of getting the SQL statement used > > to form a given table, one would get the name, the columns, and all > > manner of info about those columns. > > What about a "PRAGMA table_info(table-name)" query? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
