Neil Conway <[EMAIL PROTECTED]> writes:
> Second question: SQL92 also specifies this for SET CONSTRAINTS --
> 1) If an SQL-transaction is currently active, then let TXN be the
>currently active SQL-transaction. Otherwise, let TXN be the next
>SQL-transaction for the SQL-agent.
On Fri, 3 May 2002, Neil Conway wrote:
> On Fri, 3 May 2002 10:39:28 -0700 (PDT)
> "Stephan Szabo" <[EMAIL PROTECTED]> wrote:
> >
> > On Fri, 3 May 2002, Neil Conway wrote:
> > > My reading of this: if you specify ALL, only the constraints marked
> > > as DEFERRABLE are affected. If you specify
On Fri, 3 May 2002 10:39:28 -0700 (PDT)
"Stephan Szabo" <[EMAIL PROTECTED]> wrote:
>
> On Fri, 3 May 2002, Neil Conway wrote:
> > My reading of this: if you specify ALL, only the constraints marked
> > as DEFERRABLE are affected. If you specify a specific constraint,
> > it is deferred, whether t
On Fri, 3 May 2002, Neil Conway wrote:
> Hi all,
>
> The SQL92 spec has this to say about SET CONSTRAINTS DEFERRED:
>
> a) If ALL is specified, then the constraint mode in TXN of all
>constraints that are DEFERRABLE is set to deferred.
>
> b) Otherwise, the constraint mode in TXN
Hi all,
The SQL92 spec has this to say about SET CONSTRAINTS DEFERRED:
a) If ALL is specified, then the constraint mode in TXN of all
constraints that are DEFERRABLE is set to deferred.
b) Otherwise, the constraint mode in TXN for the constraints
identified by the s in the
