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

Re: function side effects

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 (view raw or flat)
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.


In response to

pgsql-hackers by date

Next:From: tmpDate: 2010-03-02 10:31:58
Subject: How far are projections pushed down the execution tree?
Previous:From: Peter EisentrautDate: 2010-03-02 10:26:20
Subject: Re: function side effects

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