Andre,
the strange behavior may have been due to the same bug Alex
Baumeister reported, and for which I posted a fix on the mailing
list a few minutes ago.
After you had reloaded the table, did you insert, update, or delete
any rows in the table? Or did you just do selects? Did you have any
othe
Heikki, here are more details ...
I' am running mysql-3.23.37 on a hp-ux11 box (with actual patches)
I used the following configure options to compile MySQL:
CXX=gcc
CFLAGS="-fomit-frame-pointer -O6 -fpic"
CXXFLAGS="-felide-constructors -fno-exceptions -fno-rtti -O6"
./configure --with-low-m
Andre,
it might be a bug in the multiversioning code in InnoDB.
Can you describe in detail the situation:
- What is the CREATE TABLE statement?
- How many rows there are in the table?
- How did you import the table?
- Are you able to repeat the bug if you delete and drop the table,
and create
Hi,
I accidently delete all my records from a table, but I always make backups!!!
Okay, I deleted the (empty) table with drop table.
Than I recreate the table and all the data mith a mysql batch job (from
mysqldump) .
No problem. Than I started the mysql UI and make some test queries.
select *
