From: | "Scot L(dot) Harris" <webid(at)cfl(dot)rr(dot)com> |
---|---|
To: | Andrew McMillan <andrew(at)catalyst(dot)net(dot)nz> |
Cc: | pgsql-php(at)postgresql(dot)org |
Subject: | Re: table column information |
Date: | 2004-05-17 21:31:44 |
Message-ID: | 1084829504.2059.187.camel@lathe |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-php |
On Mon, 2004-05-17 at 06:26, Andrew McMillan wrote:
> On Sun, 2004-05-16 at 23:16 -0400, Scot L. Harris wrote:
> > >
> > > You can also select the column names from the database metadata
> > > directly:
> > >
> > > SELECT attname
> > > FROM pg_class c join pg_attribute a on c.oid = a.attrelid
> > > WHERE c.relname = '<your table name>'
> > > AND a.attnum >= 0;
> > >
> > > This approach won't get killed by the efficiency problems above.
> > >
> > > Cheers,
> > > Andrew.
> >
> When I want to figure out something like this I tend to use "psql -E" so
> that all queries are echoed before being sent to the backend. Then I do
> something like "\d <table>" and see what SQL psql generates internally.
>
> Also, dig here for detailed information on the postgresql data
> dictionary tables:
>
> http://www.postgresql.org/docs/7.4/interactive/catalogs.html
>
> the most useful ones are pg_class and pg_attribute usually (for obvious
> reasons :-). With 7.4 I also find myself looking at the
> pg_stat_activity view from time to time as well.
>
> Cheers,
> Andrew.
Thanks to everyone that responded to my question. I have my application
working as I wanted. I really appreciate all the help that was
provided.
--
Scot L. Harris <webid(at)cfl(dot)rr(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Treat | 2004-05-18 21:53:35 | Re: table column information |
Previous Message | Steve Crawford | 2004-05-17 17:47:49 | Re: table column information |