From: Gary Stainburn <gary.stainburn@ringways.co.uk>
Organization: Ringways Garages Ltd
To: pgsql-sql@postgresql.org
Subject: Re: unique key problem on update
Date: Fri, 20 Sep 2013 17:30:50 +0100
User-Agent: KMail/1.9.10
Cc: Thomas Kellerer <spam_eater@gmx.net>
References: <201309201707.56028.gary.stainburn@ringways.co.uk>
 <l1ht05$9cq$1@ger.gmane.org>
In-Reply-To: <l1ht05$9cq$1@ger.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <201309201730.50960.gary.stainburn@ringways.co.uk>
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

On Friday 20 September 2013 17:26:58 Thomas Kellerer wrote:
> You need to define the primary key as deferrable:
>
> create table skills_pages
> (
>   sp_id        serial not null,
>   sp_sequence  integer not null,
>   sp_title     character varying(80),
>   sp_narative  text,
>   primary key (sp_id) deferrable
> );

Cheers. I'll look at that. It's actually the second unique index that's the 
problem but I'm guessing I can set that index up as deferrable too.

Hopefully it'll work for mysql too.

-- 
Gary Stainburn
Group I.T. Manager
Ringways Garages
http://www.ringways.co.uk 


-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql