| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, Greg Stark <gsstark(at)mit(dot)edu>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Tatsuo Ishii <ishii(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: function side effects |
| Date: | 2010-03-02 10:28:26 |
| Message-ID: | 1267525706.20952.7.camel@fsopti579.F-Secure.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On mån, 2010-03-01 at 16:29 -0500, Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > SQL standard:
>
> > <SQL-data access indication> ::=
> > NO SQL
> > | CONTAINS SQL
> > | READS SQL DATA
> > | MODIFIES SQL DATA
>
> Huh. I understand three of those, but what is the use of CONTAINS SQL?
My reading is that CONTAINS SQL allows/indicates the use of non-data
statements such as CREATE or ALTER, whereas READS SQL DATA and MODIFIES
SQL DATA specifically refer to reading or writing table data.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | tmp | 2010-03-02 10:31:58 | How far are projections pushed down the execution tree? |
| Previous Message | Peter Eisentraut | 2010-03-02 10:26:20 | Re: function side effects |