| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Paul DuBois | Date: | January 20 2003 6:03pm |
| Subject: | Re: 3.23 doesn't report dup key on INSERT ... SELECT | ||
| View as plain text | |||
At 12:29 -0500 1/20/03, Bill Easton wrote: >It appears that the stable, production version, 3.23 doesn't give an SQL >error when an INSERT ... SELECT would cause a duplicate primary key. I believe the default behavior for INSERT ... SELECT is like INSERT IGNORE ... SELECT for 3.23. > 4.0 >does not appear to have the problem. (I discovered it when replicating from >3.23.49 Linux to a 4.0.1 Windows 2000--the server did not detect the >duplicate key, but replication crashed.)
| Thread | ||
|---|---|---|
| • 3.23 doesn't report dup key on INSERT ... SELECT | Bill Easton | 20 Jan |
| • Re: 3.23 doesn't report dup key on INSERT ... SELECT | Paul DuBois | 20 Jan |
