Skip site navigation (1) Skip section navigation (2)

Re: pgsql-server/ oc/src/sgml/runtime.sgml rc/back ...

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql-server/ oc/src/sgml/runtime.sgml rc/back ...
Date: 2003-10-04 23:01:35
Message-ID: Pine.LNX.4.44.0310050057150.2745-100000@peter.localdomain (view raw, whole thread or download thread mbox)
Lists: pgsql-committerspgsql-hackers
Tom Lane writes:

> > If it's only honored by SQL functions, then it should probably be called
> > check_sql_function_bodies.
> I thought about that while I was making the patch, but decided that it
> would be a very un-forward-looking name.  Someday we will probably have
> syntax-checking validators for plpgsql, etc.

The point of this feature is to avoid failures because of forward
references in SQL code.  A syntax-checking validator in anything but
possibly plpgsql will not even look at SQL code, so a validator for
a different language will only gain pain and confusion by respecting this
parameter.  Perhaps it needs to different name altogether, along the lines
of "do not check SQL code in functions".

Peter Eisentraut   peter_e(at)gmx(dot)net

In response to


pgsql-hackers by date

Next:From: Andrew DunstanDate: 2003-10-04 23:15:15
Subject: Re: [HACKERS] initdb
Previous:From: Joshua D. DrakeDate: 2003-10-04 22:00:13
Subject: Re: max_connections/shared_buffers (was Re: Beta4 Tag'd

pgsql-committers by date

Next:From: Peter EisentrautDate: 2003-10-04 23:04:18
Subject: Re: pgsql-server/ oc/src/sgml/libpq.sgml rc/interf ...
Previous:From: Peter Eisentraut - PostgreSQLDate: 2003-10-04 22:50:20
Subject: pgsql-server/src/backend/po es.po

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group