Re: AW: New SQL Datatype RECURRINGCHAR

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Hannu Krosing <hannu(at)tm(dot)ee>, Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: AW: New SQL Datatype RECURRINGCHAR
Date: 2001-07-09 21:44:27
Message-ID: Pine.LNX.4.30.0107092339290.677-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane writes:

> SQL92 gives this restriction on WHERE clauses for updatable views:
>
> d) If the <table expression> immediately contained in QS imme-
> diately contains a <where clause> WC, then no leaf generally
> underlying table of QS shall be a generally underlying table
> of any <query expression> contained in WC.
>
> which conveys nothing to my mind :-(, except that they're restricting
> sub-SELECTs in WHERE somehow. Can anyone translate that into English?

No table mentioned in the FROM-clause (in PG even implicitly) of the query
expression (or view definition) is allowed to be mentioned in a subquery
in the WHERE clause of the query expression (or view definition).

The phrasing "leaf" and "generally" underlying is only to make this
statement theoretically pure because you can create generally underlying
tables that look different but do the same thing (different join syntax),
whereas a leaf generally underlying table is guaranteed to be a real base
table.

--
Peter Eisentraut peter_e(at)gmx(dot)net http://funkturm.homeip.net/~peter

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Martin 2001-07-09 23:26:55 timestamp not consistent with documentation or standard
Previous Message Bruce Momjian 2001-07-09 21:37:19 Re: create user problem