Running 5.1.34 on XP
Box has been working for form some time, however last night it
asserted out. I've attached the log output, below. I've taken the
query, that is listed, and run it without any trouble -- its only
issue being that it could use some rewriting.
I'd greatly appreciate any help i
(0)7812 451238
> Email j...@butterflysystems.co.uk
>
> Certified MySQL 5 Database Administrator (CMDBA)
> Certified MySQL 5 Developer
> Cognos BI Developer
>
> ---
> Sent from HP IPAQ mobile device.
>
>
>
> -Original Message-
> From: Proemial
>
> Regards
>
> John Daisley
> Mobile +44(0)7812 451238
> Email j...@butterflysystems.co.uk
>
> Certified MySQL 5 Database Administrator (CMDBA)
> Certified MySQL 5 Developer
> Cognos BI Developer
>
> ---
> Sent from HP IPAQ mobile device.
I run a process which loads a series of timestamped data into a table.
I use the TIMESTAMP column.
I have a single value with a timestamp of '2008-03-9 2:56:34.737'
which fails on insert with 'incorrect datetime'. Days before, and
after work. Hours later in the day work. I thought it might be
ther transaction starts, mine fails, the other
> completes and commit's, it has to get ID #3 and not ID #1. At the time the
> transaction was taking place, ID #1 and #2 were in use.
>
> Essentially, your SQL statement is a single transaction with AUTO_COMMIT set
> to '1'.
Hey folks. I'm getting some weird behaviour out of Auto_increment.
If I enter a attempt to INSERT a row into a table with a UNIQUE index,
where the insert would violate uniqueness of existing data, I'm seeing
the auto_increment increase even though the insert fails.
The server in question is 5.1.
I'm trying to resolve a frustrating replication problem with my databases.
The master contains a number of schema, only using Innodb tables.
Updates happen regularly, usually using bulk inserts of the form
INSERT ... ON DUPLICATE UPDATE. Data is mostly numbers. The missing
queries contain no non
