Re: SQL standard changed behavior of ON UPDATE SET NULL/SET DEFAULT?

From: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: SQL standard changed behavior of ON UPDATE SET NULL/SET DEFAULT?
Date: 2012-06-16 20:28:45
Message-ID: CAEZATCX3-GUhpaBWDCB+-nLE1a1OU5OP=n1n+W9+Rc1o3FS5ZA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 16 June 2012 21:18, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Anybody have DB2, or something else that might be thought to be pretty
> close to spec-compliant?
>

I have an Oracle DB, but they're not exactly known for spec
compliance. In fact they dodge this entire issue by not supporting ON
UPDATE actions at all :-)

Regards,
Dean

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-06-16 21:38:18 s/UNSPECIFIED/SIMPLE/ in foreign key code?
Previous Message Tom Lane 2012-06-16 20:18:48 Re: SQL standard changed behavior of ON UPDATE SET NULL/SET DEFAULT?