| From: | Jochem van Dieten <jochemd(at)oli(dot)tudelft(dot)nl> |
|---|---|
| To: | Medi Montaseri <medi(dot)montaseri(at)intransa(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: What is best way to query presence of a table |
| Date: | 2003-01-03 02:23:19 |
| Message-ID: | 3E14F417.5050705@oli.tudelft.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> Subject: What is best way to query presence of a table
> From: Medi Montaseri <medi(dot)montaseri(at)intransa(dot)com>
> Date: Thu, 02 Jan 2003 16:45:37 -0800
> To: pgsql-general <pgsql-general(at)postgresql(dot)org>
>
> What is the best way to query presence of a table
> I'd like to solve this such that I'm protected from internal changes
> within PG.
You might want to grab the INFORMATION_SCHEMA patch from the current
source (src/backend/catalog) and apply that (after removing the check
constraint on the domain, I think it is not implemented in 7.3). That
would give you a method that should be safe for the future and portable
to other databases.
Jochem
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hadley Willan | 2003-01-03 02:24:13 | Re: no space left on device |
| Previous Message | Bruce Momjian | 2003-01-03 02:03:48 | Re: ODBC - adding missing FROM clause entry |