hello everybody,
we are facing strange problems since we dumped tables from 3.22.22 (isam)
mysql and imported them into 3.23.32 (myisam) last friday;
this problem also occured when we selected into outfile from 3.22.22 and
then loaded data infile to 3.23.32;
first, everything seemed to go ok; all tables were there with all data
in it (all new *.myd, *.myi and *.frm were there);
then we went into sunny weekend, and when we came back on monday suddenly
all *.myd files were empty... (this must have been happened
already on friday, because on our backup it was also empty...);
has anybody a reason for this happening?
can we restore the data in some way? the *.myi and *.frm files were not
empty..
so now we are thinking about upgrading to mysql-max (with transaction
support);
we are using suse linux 7.1; is it possible to use mysql-max with already
installed mysql-shared, mysql-client and  mysql-devel packets?
thanx for your help in advance,
greetings,
thoni bernhard



---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to