From: | Hannu Krosing <hannu(at)tm(dot)ee> |
---|---|
To: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
Cc: | "'Mike Mascari'" <mascarm(at)mascari(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: AW: Possible feature? |
Date: | 2001-07-11 12:58:59 |
Message-ID: | 3B4C4D93.AA4F8936@tm.ee |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Zeugswetter Andreas SB wrote:
>
> On the other hand, what hinders you from using a "speaking" name for the
> constraint ?
>
> postgres=# create table aa (id int, constraint "for Social Security number" unique (id));
> NOTICE: CREATE TABLE/UNIQUE will create implicit index 'for Social Security number' for table 'aa'
> CREATE
> postgres=# insert into aa values (1);
> INSERT 23741 1
> postgres=# insert into aa values (1);
> ERROR: Cannot insert a duplicate key into unique index for Social Security number
I might want the message to be in some other language ...
I might even want the language to depend on CURRENT_USER.
-------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Tony Grant | 2001-07-11 13:06:57 | JDBC and stored procedures |
Previous Message | Martijn van Oosterhout | 2001-07-11 12:57:39 | Re: 2 gig file size limit |