| From: | Matt Miller <mattm(at)epx(dot)com> |
|---|---|
| To: | josh(at)agliodbs(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Subject: | Re: 8.1 and syntax checking at create time |
| Date: | 2005-08-31 19:18:58 |
| Message-ID: | 1125515938.3640.23.camel@dbamm01-linux |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2005-08-31 at 11:59 -0700, Josh Berkus wrote:
> If a table does not exist, we don't want to check for that and bounce
> the function; possibly the function will only be called in a context
> where the table does exist.
The Pl/pgSQL compiler should be able to dive into SQL statements, hit
the catalog, and bounce a function because of invalid database object
references. Ideally this capability could be turned off on demand.
I am thankful that Oracle's PL/SQL compiler checks these things for me.
I don't remember the last time I intended to write code that referenced
something that did not exist in the database. I agree,though, that some
developers might rely on such a capability in some circumstances.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2005-08-31 19:25:17 | Re: 8.1 and syntax checking at create time |
| Previous Message | Tom Lane | 2005-08-31 19:17:49 | Re: 8.1 and syntax checking at create time |