From: | "D'Arcy" "J(dot)M(dot)" Cain <darcy(at)druid(dot)net> |
---|---|
To: | Michael(dot)Ansley(at)intec(dot)co(dot)za (Ansley Michael) |
Cc: | pgsql-interfaces(at)postgreSQL(dot)org |
Subject: | Re: [INTERFACES] A few more JDBC meta-data questions... |
Date: | 1999-08-17 11:54:46 |
Message-ID: | m11GhpG-0000dbC@druid.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
Thus spake Ansley, Michael
> Most databases require that you use SQL to query for metadata. If you are
Certainly true of PostgreSQL.
> using something like DAO on a Win32 platform, then you get a nice object
> hierarchy which you can use to discover the data model, but otherwise you
> are reduced to SQL. And DAO can't give you a list of databases!! This is
While SQL has its warts, it's not bad as a base. Those queries I included
come from my PyGreSQL stuff (http://www.druid.net/pygresql/) so that I
simply do db.get_databases(), db.get_tables() or db.get_attnames(table)
to get the information.
> something that you have to have a connection for, bit of a catch22.
> However, this can normally still be written in a reasonably modular fashion.
As someone else pointed out, you always have template1 to query against
to get the full list of databases from.
--
D'Arcy J.M. Cain <darcy(at){druid|vex}.net> | Democracy is three wolves
http://www.druid.net/darcy/ | and a sheep voting on
+1 416 424 2871 (DoD#0082) (eNTP) | what's for dinner.
From | Date | Subject | |
---|---|---|---|
Next Message | Ansley, Michael | 1999-08-17 12:15:24 | RE: [INTERFACES] A few more JDBC meta-data questions... |
Previous Message | Ansley, Michael | 1999-08-17 11:39:54 | RE: [INTERFACES] A few more JDBC meta-data questions... |