Hi!
> "Sasha" == Sasha Pachev <[EMAIL PROTECTED]> writes:
Sasha> On Wednesday 01 May 2002 11:34 pm, Jeremy Zawodny wrote:
>> After even more tracking stuff down, I managed to isolate it to a
>> change made in MySQL 4.0.1. ?The query in question was doing:
>>
>> ? INSERT INTO ... SELECT ...
On Fri, May 03, 2002 at 11:46:42AM -0600, Sasha Pachev wrote:
> On Wednesday 01 May 2002 11:34 pm, Jeremy Zawodny wrote:
> > After even more tracking stuff down, I managed to isolate it to a
> > change made in MySQL 4.0.1. ?The query in question was doing:
> >
> > ? INSERT INTO ... SELECT ...
> >
On Wednesday 01 May 2002 11:34 pm, Jeremy Zawodny wrote:
> After even more tracking stuff down, I managed to isolate it to a
> change made in MySQL 4.0.1. ?The query in question was doing:
>
> ? INSERT INTO ... SELECT ...
>
> rather than
>
> ? INSERT IGNORE INTO ... SELECT ...
>
> MySQL 3.23.x
1On Fri, Apr 26, 2002 at 09:11:52AM -0700, Jeremy Zawodny wrote:
> I started it up and it ran for about a day before it ran into a
> duplicate key error. The 3.23.47 slave hasn't hit the duplicate key
> error, nor have any of our other slaves. So it is a 4.0.2 bug of
> some sort.
This has been
