Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Carsten Gehling writes: > I'm back now, and have tested the 3.23.40. It works like a charm :-) Nice > work! > > Now I only wait for the Win32 binary to be released. I didn't think there > were any delays between the releasins anymore? > > - Carsten > Thanks for the compliments. Win32 binaries will be soon. Some InnoDB problems have to be solved first. -- Regards, __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic <[EMAIL PROTECTED]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, FullTime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus <___/ www.mysql.com - 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
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
I'm back now, and have tested the 3.23.40. It works like a charm :-) Nice work! Now I only wait for the Win32 binary to be released. I didn't think there were any delays between the releasins anymore? - Carsten - Original Message - From: "Sergei Golubchik" <[EMAIL PROTECTED]> To: "Carsten Gehling" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, July 20, 2001 1:49 PM Subject: Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields > Hi! > > 3.23 (but 4.0 hasn't that bug either). > > Will be 2.23.40 soon. > > And have nice trip, btw. > > On Jul 20, Carsten Gehling wrote: > > Which dev. tree is that? 3.23 or 4.0? > > > > - Carsten (who hasn't left yet ;-) > > > > - Original Message - > > From: "Sergei Golubchik" <[EMAIL PROTECTED]> > > Subject: Re: Bug report: FULLTEXT index corrupts the index with too many > > > > > Hi! > > > > > > Ok, confirmed (finally :-) ) > > > > > > My fault was that I was using our latest developmnet tree. > > > When I've tried this on 3.23.39 as went public, the bug appeared. > > > > > > So, looks like the bug was fixed even before it was found :-) > > > Probably, it is somehow related to over bug I've fixed > > > since 3.23.39 release. > > > > > > On Jul 20, Carsten Gehling wrote: > > > > I'm going to Spain today and cannot respond to any questions in the next > > > > week. I was going to wait with this until I got home again, but what the > > > > heck ;-) > > > > > > > > Run the following script through your MySQL on an empty database with > > > > > > > > mysql -uusername -ppassword dbname > > > > > > > and the last command should produce the following error: > > > > > > > > ERROR 1034 at line 31: Incorrect key file for table: 'visitkort'. Try to > > > > repair it > > > > > > > Regards, > > > Sergei > > > > > > -- > > > MySQL Development Team > > >__ ___ ___ __ > > > / |/ /_ __/ __/ __ \/ / Sergei Golubchik <[EMAIL PROTECTED]> > > > / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ > > > /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany > > ><___/ > > > > > > Regards, > Sergei > > -- > MySQL Development Team >__ ___ ___ __ > / |/ /_ __/ __/ __ \/ / Sergei Golubchik <[EMAIL PROTECTED]> > / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ > /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany ><___/ > > - > 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 > > - 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
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Take a look at : http://www.mysql.com/doc/I/n/Installing_source_tree.html - Original Message - From: "Simon Green" <[EMAIL PROTECTED]> To: "'Fournier Jocelyn [Presence-PC]'" <[EMAIL PROTECTED]>; "Carsten Gehling" <[EMAIL PROTECTED]>; "Sergei Golubchik" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, July 20, 2001 2:55 PM Subject: RE: Bug report: FULLTEXT index corrupts the index with too many TEXT fields > Hi > Where can we get V4.0? > > Thanks Simon > > -Original Message- > From: Fournier Jocelyn [Presence-PC] [mailto:[EMAIL PROTECTED]] > Sent: 20 July 2001 12:30 > To: Carsten Gehling; Sergei Golubchik > Cc: [EMAIL PROTECTED] > Subject: Re: Bug report: FULLTEXT index corrupts the index with too many > TEXT fields > > > Hi, > > I've just tested with MySQL 4.0, no error, but strange result : > > mysql> insert into visitkort (kategori_id) values (108); > Query OK, 1 row affected (0.00 sec) > > mysql> update visitkort set navn = 'test5' where id = last_insert_id(); > Query OK, 1 row affected (0.00 sec) > Rows matched: 1 Changed: 1 Warnings: 0 > > mysql> update visitkort set tekst1 = 'bla bla' where id = last_insert_id(); > Query OK, 1 row affected (0.00 sec) > Rows matched: 1 Changed: 1 Warnings: 0 > > The latest update seems to have been successful, but if you look at the > table you can see the tekst1 field has not been updated : > > ++-+---+---+-++-+-+---+- > -+-+-+---+--+--+-+ -- > --++++ > | id | kategori_id | aktiv | navn | adresse | postnr | tlf | fax | email | > password | url | beskrivelse | visitkort | skabelon | logo | billede | > tekst1 | tekst2 | tekst3 | tekst4 | > ++-+---+---+-++-+-+---+- > -+-+-+---+--+--+-+ -- > --++++ > | 1 | 108 | 0 | test5 | || | | | > | | | 0 |0 |0 | 0 || > ||| > ++-+---+---+-++-+-+---+- > -+-+-+---+--+--+-+ -- > --+++----+ > > Regards, > > Jocelyn Fournier > Presence-PC > > - Original Message - > From: "Carsten Gehling" <[EMAIL PROTECTED]> > To: "Sergei Golubchik" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Friday, July 20, 2001 12:06 PM > Subject: Re: Bug report: FULLTEXT index corrupts the index with too many > TEXT fields > > > > I'm going to Spain today and cannot respond to any questions in the next > > week. I was going to wait with this until I got home again, but what the > > heck ;-) > > > > Run the following script through your MySQL on an empty database with > > > > mysql -uusername -ppassword dbname > > > and the last command should produce the following error: > > > > ERROR 1034 at line 31: Incorrect key file for table: 'visitkort'. Try to > > repair it > > > > I've let 3 people besides myself test it, and they all get the same error. > > It has now been tested on: > > > > Win2k server SP2, MySQL 3.23.32 > > > > Win2k server SP2, MySQL 3.23.39 > > > > Win2k Pro (Danish), MySQL 3.23.33 (normal version) > > > > Win2k Pro SP2 (English), MySQL 3.23.38-MAX > > > > Debian GNU/Linux, MySQL 3.23.39 (bniary .deb package) > > > > Some other Linux (didn't get the distro name), MySQL 3.23.39 > > > > All of the above produces the error. So something must be wrong. > > > > Sincerily, > > - Carsten > > > > Here's the script: > > > > ## > > CREATE TABLE `visitkort` ( > > `id` int(10) unsigned NOT NULL auto_increment, > > `kategori_id` int(10) unsigned NOT NULL default '0', > > `aktiv` tinyint(3) unsigned NOT NULL default '0', > > `navn` varchar(60) NOT NULL default '', > > `adresse` varchar(150) NOT NULL default '', > > `postnr` varchar(5) NOT NULL default '', > > `tlf` varchar(20) NOT NULL default '', > > `fax` varchar(20) NOT NULL default '', > > `email` varchar(60) NOT NULL default '', > > `password` varchar(20) NOT NULL default '', > &g
RE: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Hi Where can we get V4.0? Thanks Simon -Original Message- From: Fournier Jocelyn [Presence-PC] [mailto:[EMAIL PROTECTED]] Sent: 20 July 2001 12:30 To: Carsten Gehling; Sergei Golubchik Cc: [EMAIL PROTECTED] Subject: Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields Hi, I've just tested with MySQL 4.0, no error, but strange result : mysql> insert into visitkort (kategori_id) values (108); Query OK, 1 row affected (0.00 sec) mysql> update visitkort set navn = 'test5' where id = last_insert_id(); Query OK, 1 row affected (0.00 sec) Rows matched: 1 Changed: 1 Warnings: 0 mysql> update visitkort set tekst1 = 'bla bla' where id = last_insert_id(); Query OK, 1 row affected (0.00 sec) Rows matched: 1 Changed: 1 Warnings: 0 The latest update seems to have been successful, but if you look at the table you can see the tekst1 field has not been updated : ++-+---+---+-++-+-+---+- -+-+-+---+--+--+-+-- --++++ | id | kategori_id | aktiv | navn | adresse | postnr | tlf | fax | email | password | url | beskrivelse | visitkort | skabelon | logo | billede | tekst1 | tekst2 | tekst3 | tekst4 | ++-+---+---+-++-+-+---+- -+-+-+---+--+--+-+-- --++++ | 1 | 108 | 0 | test5 | || | | | | | | 0 |0 |0 | 0 || ||| ++-+---+---+-++-+-+---+- -+-+-+---+--+--+-+-- --++++ Regards, Jocelyn Fournier Presence-PC - Original Message - From: "Carsten Gehling" <[EMAIL PROTECTED]> To: "Sergei Golubchik" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, July 20, 2001 12:06 PM Subject: Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields > I'm going to Spain today and cannot respond to any questions in the next > week. I was going to wait with this until I got home again, but what the > heck ;-) > > Run the following script through your MySQL on an empty database with > > mysql -uusername -ppassword dbname > and the last command should produce the following error: > > ERROR 1034 at line 31: Incorrect key file for table: 'visitkort'. Try to > repair it > > I've let 3 people besides myself test it, and they all get the same error. > It has now been tested on: > > Win2k server SP2, MySQL 3.23.32 > > Win2k server SP2, MySQL 3.23.39 > > Win2k Pro (Danish), MySQL 3.23.33 (normal version) > > Win2k Pro SP2 (English), MySQL 3.23.38-MAX > > Debian GNU/Linux, MySQL 3.23.39 (bniary .deb package) > > Some other Linux (didn't get the distro name), MySQL 3.23.39 > > All of the above produces the error. So something must be wrong. > > Sincerily, > - Carsten > > Here's the script: > > ## > CREATE TABLE `visitkort` ( > `id` int(10) unsigned NOT NULL auto_increment, > `kategori_id` int(10) unsigned NOT NULL default '0', > `aktiv` tinyint(3) unsigned NOT NULL default '0', > `navn` varchar(60) NOT NULL default '', > `adresse` varchar(150) NOT NULL default '', > `postnr` varchar(5) NOT NULL default '', > `tlf` varchar(20) NOT NULL default '', > `fax` varchar(20) NOT NULL default '', > `email` varchar(60) NOT NULL default '', > `password` varchar(20) NOT NULL default '', > `url` varchar(150) NOT NULL default '', > `beskrivelse` varchar(200) NOT NULL default '', > `visitkort` tinyint(3) unsigned NOT NULL default '0', > `skabelon` tinyint(3) unsigned NOT NULL default '0', > `logo` tinyint(3) unsigned NOT NULL default '0', > `billede` tinyint(3) unsigned NOT NULL default '0', > `tekst1` text NOT NULL, > `tekst2` text NOT NULL, > `tekst3` text NOT NULL, > `tekst4` text NOT NULL, > PRIMARY KEY (`id`), > FULLTEXT KEY `ft` > (`navn`,`beskrivelse`,`tekst1`,`tekst2`,`tekst3`,`tekst4`) > ) TYPE=MyISAM; > > insert into visitkort (kategori_id) values (108); > > update visitkort set navn = 'test5' where id = last_insert_id(); > > update visitkort set tekst1 = 'bla bla' where id = last_insert_id(); > ## > > > > > >
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Hi! 3.23 (but 4.0 hasn't that bug either). Will be 2.23.40 soon. And have nice trip, btw. On Jul 20, Carsten Gehling wrote: > Which dev. tree is that? 3.23 or 4.0? > > - Carsten (who hasn't left yet ;-) > > - Original Message - > From: "Sergei Golubchik" <[EMAIL PROTECTED]> > Subject: Re: Bug report: FULLTEXT index corrupts the index with too many > > > Hi! > > > > Ok, confirmed (finally :-) ) > > > > My fault was that I was using our latest developmnet tree. > > When I've tried this on 3.23.39 as went public, the bug appeared. > > > > So, looks like the bug was fixed even before it was found :-) > > Probably, it is somehow related to over bug I've fixed > > since 3.23.39 release. > > > > On Jul 20, Carsten Gehling wrote: > > > I'm going to Spain today and cannot respond to any questions in the next > > > week. I was going to wait with this until I got home again, but what the > > > heck ;-) > > > > > > Run the following script through your MySQL on an empty database with > > > > > > mysql -uusername -ppassword dbname > > > > > and the last command should produce the following error: > > > > > > ERROR 1034 at line 31: Incorrect key file for table: 'visitkort'. Try to > > > repair it > > > > > Regards, > > Sergei > > > > -- > > MySQL Development Team > >__ ___ ___ __ > > / |/ /_ __/ __/ __ \/ / Sergei Golubchik <[EMAIL PROTECTED]> > > / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ > > /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany > ><___/ > > > Regards, Sergei -- MySQL Development Team __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sergei Golubchik <[EMAIL PROTECTED]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany <___/ - 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
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Which dev. tree is that? 3.23 or 4.0? - Carsten (who hasn't left yet ;-) - Original Message - From: "Sergei Golubchik" <[EMAIL PROTECTED]> To: "Carsten Gehling" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, July 20, 2001 1:22 PM Subject: Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields > Hi! > > Ok, confirmed (finally :-) ) > > My fault was that I was using our latest developmnet tree. > When I've tried this on 3.23.39 as went public, the bug appeared. > > So, looks like the bug was fixed even before it was found :-) > Probably, it is somehow related to over bug I've fixed > since 3.23.39 release. > > On Jul 20, Carsten Gehling wrote: > > I'm going to Spain today and cannot respond to any questions in the next > > week. I was going to wait with this until I got home again, but what the > > heck ;-) > > > > Run the following script through your MySQL on an empty database with > > > > mysql -uusername -ppassword dbname > > > and the last command should produce the following error: > > > > ERROR 1034 at line 31: Incorrect key file for table: 'visitkort'. Try to > > repair it > > > Regards, > Sergei > > -- > MySQL Development Team >__ ___ ___ __ > / |/ /_ __/ __/ __ \/ / Sergei Golubchik <[EMAIL PROTECTED]> > / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ > /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany ><___/ > - 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
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Hi, I've just tested with MySQL 4.0, no error, but strange result : mysql> insert into visitkort (kategori_id) values (108); Query OK, 1 row affected (0.00 sec) mysql> update visitkort set navn = 'test5' where id = last_insert_id(); Query OK, 1 row affected (0.00 sec) Rows matched: 1 Changed: 1 Warnings: 0 mysql> update visitkort set tekst1 = 'bla bla' where id = last_insert_id(); Query OK, 1 row affected (0.00 sec) Rows matched: 1 Changed: 1 Warnings: 0 The latest update seems to have been successful, but if you look at the table you can see the tekst1 field has not been updated : ++-+---+---+-++-+-+---+- -+-+-+---+--+--+-+-- --++++ | id | kategori_id | aktiv | navn | adresse | postnr | tlf | fax | email | password | url | beskrivelse | visitkort | skabelon | logo | billede | tekst1 | tekst2 | tekst3 | tekst4 | ++-+---+---+-++-+-+---+- -+-+-+---+--+--+-+-- --++++ | 1 | 108 | 0 | test5 | || | | | | | | 0 |0 |0 | 0 || ||| ++-+---+---+-++-+-+---+- -+-+-+---+--+--+-+-- --++++ Regards, Jocelyn Fournier Presence-PC - Original Message - From: "Carsten Gehling" <[EMAIL PROTECTED]> To: "Sergei Golubchik" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, July 20, 2001 12:06 PM Subject: Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields > I'm going to Spain today and cannot respond to any questions in the next > week. I was going to wait with this until I got home again, but what the > heck ;-) > > Run the following script through your MySQL on an empty database with > > mysql -uusername -ppassword dbname > and the last command should produce the following error: > > ERROR 1034 at line 31: Incorrect key file for table: 'visitkort'. Try to > repair it > > I've let 3 people besides myself test it, and they all get the same error. > It has now been tested on: > > Win2k server SP2, MySQL 3.23.32 > > Win2k server SP2, MySQL 3.23.39 > > Win2k Pro (Danish), MySQL 3.23.33 (normal version) > > Win2k Pro SP2 (English), MySQL 3.23.38-MAX > > Debian GNU/Linux, MySQL 3.23.39 (bniary .deb package) > > Some other Linux (didn't get the distro name), MySQL 3.23.39 > > All of the above produces the error. So something must be wrong. > > Sincerily, > - Carsten > > Here's the script: > > ## > CREATE TABLE `visitkort` ( > `id` int(10) unsigned NOT NULL auto_increment, > `kategori_id` int(10) unsigned NOT NULL default '0', > `aktiv` tinyint(3) unsigned NOT NULL default '0', > `navn` varchar(60) NOT NULL default '', > `adresse` varchar(150) NOT NULL default '', > `postnr` varchar(5) NOT NULL default '', > `tlf` varchar(20) NOT NULL default '', > `fax` varchar(20) NOT NULL default '', > `email` varchar(60) NOT NULL default '', > `password` varchar(20) NOT NULL default '', > `url` varchar(150) NOT NULL default '', > `beskrivelse` varchar(200) NOT NULL default '', > `visitkort` tinyint(3) unsigned NOT NULL default '0', > `skabelon` tinyint(3) unsigned NOT NULL default '0', > `logo` tinyint(3) unsigned NOT NULL default '0', > `billede` tinyint(3) unsigned NOT NULL default '0', > `tekst1` text NOT NULL, > `tekst2` text NOT NULL, > `tekst3` text NOT NULL, > `tekst4` text NOT NULL, > PRIMARY KEY (`id`), > FULLTEXT KEY `ft` > (`navn`,`beskrivelse`,`tekst1`,`tekst2`,`tekst3`,`tekst4`) > ) TYPE=MyISAM; > > insert into visitkort (kategori_id) values (108); > > update visitkort set navn = 'test5' where id = last_insert_id(); > > update visitkort set tekst1 = 'bla bla' where id = last_insert_id(); > ## > > > > > > - > 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 > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php > > - 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 Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
BTW: As I've stated earlier, the error goes away, if you either remove the FULLTEXT index or let the affected fields accept NULL values. - Carsten - Original Message - From: "Carsten Gehling" <[EMAIL PROTECTED]> To: "Sergei Golubchik" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, July 20, 2001 12:06 PM Subject: Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields > I'm going to Spain today and cannot respond to any questions in the next > week. I was going to wait with this until I got home again, but what the > heck ;-) > > Run the following script through your MySQL on an empty database with > > mysql -uusername -ppassword dbname > and the last command should produce the following error: > > ERROR 1034 at line 31: Incorrect key file for table: 'visitkort'. Try to > repair it > > I've let 3 people besides myself test it, and they all get the same error. > It has now been tested on: > > Win2k server SP2, MySQL 3.23.32 > > Win2k server SP2, MySQL 3.23.39 > > Win2k Pro (Danish), MySQL 3.23.33 (normal version) > > Win2k Pro SP2 (English), MySQL 3.23.38-MAX > > Debian GNU/Linux, MySQL 3.23.39 (bniary .deb package) > > Some other Linux (didn't get the distro name), MySQL 3.23.39 > > All of the above produces the error. So something must be wrong. > > Sincerily, > - Carsten > > Here's the script: > > ## > CREATE TABLE `visitkort` ( > `id` int(10) unsigned NOT NULL auto_increment, > `kategori_id` int(10) unsigned NOT NULL default '0', > `aktiv` tinyint(3) unsigned NOT NULL default '0', > `navn` varchar(60) NOT NULL default '', > `adresse` varchar(150) NOT NULL default '', > `postnr` varchar(5) NOT NULL default '', > `tlf` varchar(20) NOT NULL default '', > `fax` varchar(20) NOT NULL default '', > `email` varchar(60) NOT NULL default '', > `password` varchar(20) NOT NULL default '', > `url` varchar(150) NOT NULL default '', > `beskrivelse` varchar(200) NOT NULL default '', > `visitkort` tinyint(3) unsigned NOT NULL default '0', > `skabelon` tinyint(3) unsigned NOT NULL default '0', > `logo` tinyint(3) unsigned NOT NULL default '0', > `billede` tinyint(3) unsigned NOT NULL default '0', > `tekst1` text NOT NULL, > `tekst2` text NOT NULL, > `tekst3` text NOT NULL, > `tekst4` text NOT NULL, > PRIMARY KEY (`id`), > FULLTEXT KEY `ft` > (`navn`,`beskrivelse`,`tekst1`,`tekst2`,`tekst3`,`tekst4`) > ) TYPE=MyISAM; > > insert into visitkort (kategori_id) values (108); > > update visitkort set navn = 'test5' where id = last_insert_id(); > > update visitkort set tekst1 = 'bla bla' where id = last_insert_id(); > ## > > > > > > - > 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 > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php > > - 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 Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Hi! Ok, confirmed (finally :-) ) My fault was that I was using our latest developmnet tree. When I've tried this on 3.23.39 as went public, the bug appeared. So, looks like the bug was fixed even before it was found :-) Probably, it is somehow related to over bug I've fixed since 3.23.39 release. On Jul 20, Carsten Gehling wrote: > I'm going to Spain today and cannot respond to any questions in the next > week. I was going to wait with this until I got home again, but what the > heck ;-) > > Run the following script through your MySQL on an empty database with > > mysql -uusername -ppassword dbname > and the last command should produce the following error: > > ERROR 1034 at line 31: Incorrect key file for table: 'visitkort'. Try to > repair it > Regards, Sergei -- MySQL Development Team __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sergei Golubchik <[EMAIL PROTECTED]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany <___/ - 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
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Thanks for your bug report. I am sure Sergei will have the answer before you come back from Spain ... -- Regards, __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic <[EMAIL PROTECTED]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, FullTime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus <___/ www.mysql.com - 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
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
I'm going to Spain today and cannot respond to any questions in the next week. I was going to wait with this until I got home again, but what the heck ;-) Run the following script through your MySQL on an empty database with mysql -uusername -ppassword dbname 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 Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
SV: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Hi! >> On Jul 19, Carsten Gehling wrote: > > Finally I was able to produce a complete step-by-step to > corrupt the index > > ;-) > > > > mysql> insert into visitkort (kategori_id) values (108); > > mysql> select last_insert_id(); > > mysql> update visitkort set navn = 'test5' where id = 1; > > mysql> update visitkort set tekst1 = 'bla bla' where id = 1; > > ERROR 1034: Incorrect key file for table: 'visitkort'. Try to repair it > > Sorry, but everything works ok for me: > > mysql> update visitkort set tekst1 = 'bla bla' where id = 1; > Query OK, 1 row affected (0.00 sec) > Rows matched: 1 Changed: 1 Warnings: 0 I got exactly the same error as Carsten does when I follow the above. Mysql 3.23.38-max-nt on Windows 2000 pro SP2. Regards, Martin - 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
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Hi! On Jul 19, Carsten Gehling wrote: > Finally I was able to produce a complete step-by-step to corrupt the index > ;-) > > mysql> insert into visitkort (kategori_id) values (108); > mysql> select last_insert_id(); > mysql> update visitkort set navn = 'test5' where id = 1; > mysql> update visitkort set tekst1 = 'bla bla' where id = 1; > ERROR 1034: Incorrect key file for table: 'visitkort'. Try to repair it Sorry, but everything works ok for me: mysql> update visitkort set tekst1 = 'bla bla' where id = 1; Query OK, 1 row affected (0.00 sec) Rows matched: 1 Changed: 1 Warnings: 0 Regards, Sergei -- MySQL Development Team __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sergei Golubchik <[EMAIL PROTECTED]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany <___/ - 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
Solution (but only a temporary one) Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
After the latest post, curiosity got the better of me (which is always good in a debug situation). I tried to change all 6 fields that compose the FULLTEXT index, so that they accept NULL values. The result? The error is gone. Is this a valid solution however? I've never been a great fan of the NULL value in RDBMS' - I regard it as a necessary evil to be used sparsely. So it would be great if I did not have to convert my text fields (text & varchar) into accepting NULL. - Carsten - Original Message - From: "Sergei Golubchik" <[EMAIL PROTECTED]> To: "Carsten Gehling" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, July 16, 2001 6:26 PM Subject: Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields > Hi! > > On Jul 16, Carsten Gehling wrote: > > Description: > > A specific table (see "How-To-Repeat) with a FULLTEXT index causes errors in > > the MYI file when inserting new rows. > > > > 1) Create the following table: > > CREATE TABLE `visitkort` ( > [skip] > > ) TYPE=MyISAM; > > > > 2) Insert a row with the following statement: > > > > 3) Run myisamchk with the option --extend-check and you get the following > > myisamchk: warning: 1 clients is using or hasn't closed the table properly > > > The error does not occur, if you drop the FULLTEXT index > > Ok, I was able to repeat this, still I do not think it's a bug. > Message given by myisamchk is perfectly legal - you should not expect > MySQL to close the table immidiately when the client closes the connection. > MySQL can keep the table open to speedup access to it from, e.g., > next connection. MySQL will close the table on "FLUSH TABLE", > or when the pool of opened tables is exceeded. > > if you will add "2.5) flush table" the error message will dissapear. > if you will shutdown MySQL instead, you'll get no error, either. > if you will issue "CHECK TABLE visitkort EXTENDED" instead of using > external program myisamchk, again there will be no error message. > > So, looks like everything is ok. > > In you first message (without test case) you've also added > > > The result of this is, that if anyone is trying to update the same record > > afterwards, the index is corrupted. > > I wasn't able to reproduce that. If you have a test case for this, please, > let me know. > > Regards, > Sergei > > -- > MySQL Development Team >__ ___ ___ __ > / |/ /_ __/ __/ __ \/ / Sergei Golubchik <[EMAIL PROTECTED]> > / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ > /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany ><___/ > - 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
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Finally I was able to produce a complete step-by-step to corrupt the index ;-) Do the following in the mySQL console (with e.g. a fresh and empty table): mysql> insert into visitkort (kategori_id) values (108); Query OK, 1 row affected (0.01 sec) mysql> select last_insert_id(); +--+ | last_insert_id() | +--+ |1 | +--+ 1 row in set (0.00 sec) mysql> update visitkort set navn = 'test5' where id = 1; Query OK, 1 row affected (0.00 sec) Rows matched: 1 Changed: 1 Warnings: 0 mysql> update visitkort set tekst1 = 'bla bla' where id = 1; ERROR 1034: Incorrect key file for table: 'visitkort'. Try to repair it After this, myisamchk reports the following: D:\mysql\data\test>myisamchk --extend-check visitkort Checking MyISAM file: visitkort Data records: 1 Deleted blocks: 0 myisamchk: warning: Table is marked as crashed myisamchk: warning: 1 clients is using or hasn't closed the table properly - check file-size - check key delete-chain - check record delete-chain - check index reference - check data record references index: 1 - check data record references index: 2 - check data record references index: 3 - check data record references index: 4 - check data record references index: 5 - check data record references index: 6 - check records and index references MyISAM-table 'visitkort' is usable but should be fixed I guess this isn't the expected behavior of mySQL ;-) It should be noted, that the above behavior does not occur if I drop the FULLTEXT index. Without this index, the errors are gone and table works fine. I've also tried to remove all other indexes except the FULLTEXT and the primary key, and the error is still there. So it is definitely a problem within the FULLTEXT index. - Carsten - Original Message - From: "Sergei Golubchik" <[EMAIL PROTECTED]> To: "Carsten Gehling" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, July 16, 2001 6:26 PM Subject: Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields > Hi! > > On Jul 16, Carsten Gehling wrote: > > Description: > > A specific table (see "How-To-Repeat) with a FULLTEXT index causes errors in > > the MYI file when inserting new rows. > > > > 1) Create the following table: > > CREATE TABLE `visitkort` ( > [skip] > > ) TYPE=MyISAM; > > > > 2) Insert a row with the following statement: > > > > 3) Run myisamchk with the option --extend-check and you get the following > > myisamchk: warning: 1 clients is using or hasn't closed the table properly > > > The error does not occur, if you drop the FULLTEXT index > > Ok, I was able to repeat this, still I do not think it's a bug. > Message given by myisamchk is perfectly legal - you should not expect > MySQL to close the table immidiately when the client closes the connection. > MySQL can keep the table open to speedup access to it from, e.g., > next connection. MySQL will close the table on "FLUSH TABLE", > or when the pool of opened tables is exceeded. > > if you will add "2.5) flush table" the error message will dissapear. > if you will shutdown MySQL instead, you'll get no error, either. > if you will issue "CHECK TABLE visitkort EXTENDED" instead of using > external program myisamchk, again there will be no error message. > > So, looks like everything is ok. > > In you first message (without test case) you've also added > > > The result of this is, that if anyone is trying to update the same record > > afterwards, the index is corrupted. > > I wasn't able to reproduce that. If you have a test case for this, please, > let me know. > > Regards, > Sergei > > -- > MySQL Development Team >__ ___ ___ __ > / |/ /_ __/ __/ __ \/ / Sergei Golubchik <[EMAIL PROTECTED]> > / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ > /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany ><___/ > - 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
Re: Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Hi! On Jul 16, Carsten Gehling wrote: > Description: > A specific table (see "How-To-Repeat) with a FULLTEXT index causes errors in > the MYI file when inserting new rows. > > 1) Create the following table: > CREATE TABLE `visitkort` ( [skip] > ) TYPE=MyISAM; > > 2) Insert a row with the following statement: > > 3) Run myisamchk with the option --extend-check and you get the following > myisamchk: warning: 1 clients is using or hasn't closed the table properly > The error does not occur, if you drop the FULLTEXT index Ok, I was able to repeat this, still I do not think it's a bug. Message given by myisamchk is perfectly legal - you should not expect MySQL to close the table immidiately when the client closes the connection. MySQL can keep the table open to speedup access to it from, e.g., next connection. MySQL will close the table on "FLUSH TABLE", or when the pool of opened tables is exceeded. if you will add "2.5) flush table" the error message will dissapear. if you will shutdown MySQL instead, you'll get no error, either. if you will issue "CHECK TABLE visitkort EXTENDED" instead of using external program myisamchk, again there will be no error message. So, looks like everything is ok. In you first message (without test case) you've also added > The result of this is, that if anyone is trying to update the same record > afterwards, the index is corrupted. I wasn't able to reproduce that. If you have a test case for this, please, let me know. Regards, Sergei -- MySQL Development Team __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sergei Golubchik <[EMAIL PROTECTED]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany <___/ - 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
Bug report: FULLTEXT index corrupts the index with too many TEXT fields
Description:
A specific table (see "How-To-Repeat) with a FULLTEXT index causes errors in
the MYI file when inserting new rows.
The error only occurs when the FULLTEXT index is in the table. I've tried to
recreate the table completely, and it still occurs.
The bug is found on the following platforms/versions:
Win2k server SP2, MySQL 3.23.32
Win2k server SP2, MySQL 3.23.39
Linux, MySQL 3.23.39
How-To-Repeat:
1) Create the following table:
CREATE TABLE `visitkort` (
`id` int(10) unsigned NOT NULL auto_increment,
`kategori_id` int(10) unsigned NOT NULL default '0',
`aktiv` tinyint(3) unsigned NOT NULL default '0',
`navn` varchar(60) NOT NULL default '',
`adresse` varchar(150) NOT NULL default '',
`postnr` varchar(5) NOT NULL default '',
`tlf` varchar(20) NOT NULL default '',
`fax` varchar(20) NOT NULL default '',
`email` varchar(60) NOT NULL default '',
`password` varchar(20) NOT NULL default '',
`url` varchar(150) NOT NULL default '',
`beskrivelse` varchar(200) NOT NULL default '',
`visitkort` tinyint(3) unsigned NOT NULL default '0',
`skabelon` tinyint(3) unsigned NOT NULL default '0',
`logo` tinyint(3) unsigned NOT NULL default '0',
`billede` tinyint(3) unsigned NOT NULL default '0',
`tekst1` text NOT NULL,
`tekst2` text NOT NULL,
`tekst3` text NOT NULL,
`tekst4` text NOT NULL,
PRIMARY KEY (`id`),
KEY `kategori_id` (`kategori_id`),
KEY `bruger_id` (`visitkort`),
KEY `postnr` (`postnr`),
KEY `email` (`email`),
FULLTEXT KEY `ft`
(`navn`,`beskrivelse`,`tekst1`,`tekst2`,`tekst3`,`tekst4`)
) TYPE=MyISAM;
2)
Insert a row with the following statement:
insert into visitkort (navn, kategori_id) values ('test7', 106);
3) Run myisamchk with the option --extend-check and you get the following
result
C:\mysql\data\midtfyn>myisamchk --extend-check visitkort
Checking MyISAM file: visitkort
Data records:339 Deleted blocks: 0
myisamchk: warning: 1 clients is using or hasn't closed the table properly
- check file-size
- check key delete-chain
- check record delete-chain
- check index reference
- check data record references index: 1
- check data record references index: 2
- check data record references index: 3
- check data record references index: 4
- check data record references index: 5
- check records and index references
MyISAM-table 'visitkort' is usable but should be fixed
4) To repair the table, you need to do a "flush table" and then the
myisamchk --safe-recover
C:\mysql\data\midtfyn>myisamchk --safe-recover -force visitkort
- recovering (with sort) MyISAM-table 'visitkort.MYI'
Data records: 339
- Fixing index 1
Found block with too small length at 22812; Skipped
- Fixing index 2
- Fixing index 3
- Fixing index 4
- Fixing index 5
Fix:
The error does not occur, if you drop the FULLTEXT index
Synopsis: FULLTEXT index corrupts the index with too many TEXT fields
Submitter-Id:
Originator: Carsten Gehling
Organization: Sarum
MySQL support: [none]
Severity: [serious]
Priority: [low | medium | high ]
Category: [mysqld]
Class: [sw-bug]
Release: mysql-3.23.39
Exectutable: [mysqld]
Environment: MySQL console
System:
Compiler: Binary distribution
Architecture: i
-
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
