From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Fernando Nasser <fnasser(at)redhat(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SQL flagger |
Date: | 2003-01-15 23:44:14 |
Message-ID: | Pine.LNX.4.44.0301152029270.789-100000@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Fernando Nasser writes:
> THe SQL Flagger is only required for Intermediate SQL. SQL'92 23.4 says Entry
> SQL may, but are not required to.
SQL 92 is obsolete. In SQL 99 and later it's a core feature.
> If I understood it correctly, we only need a new elog level and add a few elog
> calls in some of gram.y clauses...
As was already mentioned, you cannot evaluate run-time parameters (which
the flagger would be) in gram.y because of some transaction issues. You
need to do it in the analyze phase after the parser.
"A few" is also an optimistic statement. While the majority of the
utility commands can be rejected outright, getting the details right to a
usable degree on the rest is tricky.
--
Peter Eisentraut peter_e(at)gmx(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-01-15 23:45:22 | Re: psql and readline |
Previous Message | pgsql-bugs | 2003-01-15 23:09:58 | Bug #876: Bugs Inserts Arrays |