| From: | Thomas Lockhart <thomas(at)fourpalms(dot)org> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: Uniqueness of rule, constraint, and trigger names |
| Date: | 2002-03-11 01:37:43 |
| Message-ID: | 3C8C0A67.5EA7B830@fourpalms.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
> > The SQL spec is not a great deal of help on this, since it doesn't
> > have rules or triggers at all.
> The SQL spec has triggers, and their names are supposed to be
> globally unique.
Speaking of which, I was looking at
CREATE ASSERTION/DROP ASSERTION
in (what I think is) SQL99. It has enough restrictions on use that I'm
not yet sure what exactly it is supposed to do, and am not sure if it is
close to equivalent to something we already have. Anyone know?
- Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2002-03-11 01:41:07 | Re: Reverting SET SESSION AUTHORIZATION command |
| Previous Message | Peter Eisentraut | 2002-03-11 01:33:43 | Re: Uniqueness of rule, constraint, and trigger names |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Roberto Mello | 2002-03-11 05:02:11 | Case (in)sensitivity |
| Previous Message | Peter Eisentraut | 2002-03-11 01:33:43 | Re: Uniqueness of rule, constraint, and trigger names |