From: | "Rajesh Kumar Mallah" <mallah(dot)rajesh(at)gmail(dot)com> |
---|---|
To: | andy(dot)shellam(at)mailnetwork(dot)co(dot)uk |
Cc: | "Christopher Browne" <cbbrowne(at)acm(dot)org>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Show tables query |
Date: | 2006-04-02 15:32:09 |
Message-ID: | a97c77030604020832u23368b40r9c2637ed630c727e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 4/2/06, Andy Shellam <andy(dot)shellam(at)mailnetwork(dot)co(dot)uk> wrote:
> > After takin a swig o' Arrakan spice grog, andy(dot)shellam(at)mailnetwork(dot)co(dot)uk
> ("Andy Shellam") belched out:
> >> Is there an SQL command supported by Postgres to return a list of tables
> in a database?
>
> Sorry, did I say something wrong? I thought it was a perfectly valid
> question actually. The application in mind is going to be run exclusively
> on Postgres,
>
> so I'm not overly fussed over standards - I just wanted a quick
> win, of which Grega's SQL gave it me perfectly - tables only, nothing else
> included.
the information_schema approach is still better than querying
the system catalogs. The system catalogs are internal to postgresql
what if future versions of postgresql change the sys catalogs dramatically ?
(your app breaks!)
information_schema is the standard which are more likely to behave
the same in all versions of pgsql becoz they are(currently) views on
the sys catalogs.
Regds
Rajesh Kumar Mallah.
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andy Shellam | 2006-04-02 15:40:40 | Re: Show tables query |
Previous Message | Andy Shellam | 2006-04-02 14:53:11 | Re: Show tables query |