Re: Duplicate entry '0' for key 'PRIMARY'

On 4/16/2017 8:08 PM, the famous troll Thomas 'Pointed Head' Lahn wrote:
> J.O. Aho wrote:
>
>> From his other thread which he created afterwards:
>
> Indeed, distributing the problem description across several threads is one
> of their problems.
>
>> […]
>> He has two rows in the table which has id 0, which he has to fix before
>> he can import the data, sure he can remove the primary key restraint,
>> which will leads to his rail application may not work.
>
> More wishful thinking. One final time: He does _not_ have to fix the data
> *before* importing them. He can fix them *after* importing them, and can
> fix them *easier* this way, but not necessarily to/in the *production
> database*.
>

Once again you are wrong. It is much easier to fix a problem like this in a text file than to try to fix it in the database.

> I am not going to repeat myself any further. *Read* what the OP and I
> *wrote*, not what *you wish them to have written*, and the nonsense
> *you wish me to have written*. EOD.
>
>

Good. The op doesn't need any more of your advice on how to completely screw up his database.

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex_at_attglobal.net
==================