From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Creager <Robert_Creager(at)LogicalChaos(dot)org> |
Cc: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>, Bugs for PostgreSQL <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: Problem with domains |
Date: | 2003-09-25 05:28:29 |
Message-ID: | 1908.1064467709@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Robert Creager <Robert_Creager(at)LogicalChaos(dot)org> writes:
>> Seems like the correct behavior to me. When CONSTRAINT is given, the
>> name is not optional AFAICS.
> True, but the second CREATE DOMAIN, which is a valid form, fails when
> preceded by the invalid form. This was the error I was referring to.
> Not the fact that I didn't know how to use domains ;-) If the
> transaction is bad after the first invalid CREATE DOMAIN, the error
> should say so, rather than waiting for a second valid statement to
> come along, shouldn't it?
Uh, which part of "queries ignored until end of transaction block"
didn't you understand?
> begin;
> create domain test as integer constraint check( value > 0 );
> -- ERROR: syntax error at or near "check" at character 42
> create domain test as integer check( value > 0 );
> -- ERROR: current transaction is aborted, queries ignored until end
> of transaction block
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Creager | 2003-09-25 13:23:42 | Re: Problem with domains |
Previous Message | Stephan Szabo | 2003-09-25 05:14:11 | Re: Problem with domains |