Re: Duplicate entry '0' for key 'PRIMARY'
From: Peter H. Coffin <hellsop_at_ninehells.com>
Date: Thu, 13 Apr 2017 21:43:01 -0500
Message-ID: <slrnof0dpl.t3q.hellsop_at_nibelheim.ninehells.com>
Date: Thu, 13 Apr 2017 21:43:01 -0500
Message-ID: <slrnof0dpl.t3q.hellsop_at_nibelheim.ninehells.com>
[Quoted] [Quoted] On Tue, 11 Apr 2017 08:36:17 -0400, Jerry Stuckle wrote:
> In either case the database will be seriously borked with foreign keys
> pointing at the wrong data.
[Quoted] And that is, im my humble opinion, a point of such importance that it [Quoted] [Quoted] may as well be the ONLY point. Data integrity is paramount. Build the [Quoted] table without a primary key, FIND THE DUPLICATES, resolve them (by hand, [Quoted] if necessary) so that the data is intact and correct, THEN add the primary key back.
-- 186,000 Miles per Second. It's not just a good idea. IT'S THE LAW.Received on Fri Apr 14 2017 - 04:43:01 CEST