From: <ja...@in...> - 2006-01-26 21:48:46
|
# perl -v | grep "This is perl" This is perl, v5.8.7 built for i686-linux-thread-multi # mysql -V mysql Ver 14.7 Distrib 4.1.14, for pc-linux-gnu (i686) using readline 5.0 # cd /usr/local/slash # bin/install-slash the error is: DO: Something wrong while try to prepare query This command is not supported in the prepared statement protocol yet Error in library: Slash::Install:/usr/lib/perl5/site_perl/5.8.7/i686-linux-thread-multi/Slash/Install.pm:330:ALTER TABLE stories add fulltext (title) Which was called by: Slash::Install:/usr/lib/perl5/site_perl/5.8.7/i686-linux-thread-multi/Slash/Install.pm:153:ALTER TABLE stories add fulltext (title) Failed on :ALTER TABLE stories add fulltext (title): I think it might have something to do with this bug: http://bugs.mysql.com/bug.php?id=15665 -- |
From: shane <sh...@lo...> - 2006-01-27 00:35:25
|
On Jan 26, 2006, at 4:47 PM, ja...@in... wrote: > # perl -v | grep "This is perl" > This is perl, v5.8.7 built for i686-linux-thread-multi > # mysql -V > mysql Ver 14.7 Distrib 4.1.14, for pc-linux-gnu (i686) using > readline 5.0 > # cd /usr/local/slash > # bin/install-slash > > the error is: > > > DO: Something wrong while try to prepare query This command is not > supported in the prepared statement protocol yet > Error in library: > Slash::Install:/usr/lib/perl5/site_perl/5.8.7/i686-linux-thread- > multi/Slash/Install.pm:330:ALTER > TABLE stories add fulltext (title) > Which was called by: > Slash::Install:/usr/lib/perl5/site_perl/5.8.7/i686-linux-thread- > multi/Slash/Install.pm:153:ALTER > TABLE stories add fulltext (title) > Failed on :ALTER TABLE stories add fulltext (title): > > > I think it might have something to do with this bug: > http://bugs.mysql.com/bug.php?id=15665 No, I don't think that's it. The problem is the default table type for the table stories is MyISAM. However, with MySQL v4.x (and 5.x, so far) you can't do fulltext indexes on MyISAM tables. You can do them on InnoDB tables, however. I thought there was mention of this in the INSTALL. If not, this should be explained there. Maybe in the FAQ? Your slash installation will work, as is, even with the above errors. If you want the search to play nice, then you'll want to alter the table types for those tables and then add the fulltext indexes. Note the mention of fulltext limitations in the faq: http:// slash.lottadot.com/faqster.pl?op=view&fid=1 BTW, while you mentioned which perl and mysql you're using (which is great) you didn't mention what version of _slash_ you're using. Shane |
From: <ja...@in...> - 2006-01-27 18:01:12
|
great - thanks for the response. The version is slash-2.2.6 (for me it was obvious, the latest =) not so obvious to those who have been running slash before..) At the moment, I'm wrestling with apache and mod_perl. I'll post back with sucess or otherwise ASAP. thanks again. -- shane wrote: > > On Jan 26, 2006, at 4:47 PM, ja...@in... wrote: > >> # perl -v | grep "This is perl" >> This is perl, v5.8.7 built for i686-linux-thread-multi >> # mysql -V >> mysql Ver 14.7 Distrib 4.1.14, for pc-linux-gnu (i686) using >> readline 5.0 >> # cd /usr/local/slash >> # bin/install-slash >> >> the error is: >> >> >> DO: Something wrong while try to prepare query This command is not >> supported in the prepared statement protocol yet >> Error in library: >> Slash::Install:/usr/lib/perl5/site_perl/5.8.7/i686-linux-thread- >> multi/Slash/Install.pm:330:ALTER >> TABLE stories add fulltext (title) >> Which was called by: >> Slash::Install:/usr/lib/perl5/site_perl/5.8.7/i686-linux-thread- >> multi/Slash/Install.pm:153:ALTER >> TABLE stories add fulltext (title) >> Failed on :ALTER TABLE stories add fulltext (title): >> >> >> I think it might have something to do with this bug: >> http://bugs.mysql.com/bug.php?id=15665 > > No, I don't think that's it. The problem is the default table type > for the table stories is MyISAM. However, with MySQL v4.x (and 5.x, > so far) you can't do fulltext indexes on MyISAM tables. You can do > them on InnoDB tables, however. > > I thought there was mention of this in the INSTALL. If not, this > should be explained there. Maybe in the FAQ? > > Your slash installation will work, as is, even with the above errors. > If you want the search to play nice, then you'll want to alter the > table types for those tables and then add the fulltext indexes. Note > the mention of fulltext limitations in the faq: http:// > slash.lottadot.com/faqster.pl?op=view&fid=1 > > BTW, while you mentioned which perl and mysql you're using (which is > great) you didn't mention what version of _slash_ you're using. > > Shane > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > _______________________________________________ > Slashcode-general mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-general > > |
From: Jamie M. <ja...@mc...> - 2006-01-30 02:26:24
|
ja...@in... writes: > great - thanks for the response. The version is slash-2.2.6 (for > me it was obvious, the latest =3D) Actually it's pretty old. I'd recommend going with the most recent R_ tag from CVS, R_2_5_0_74 as of right now. We should do a new release as a tarball but we've been very focused on development and just keep putting code out in CVS instead. I'm not 100% sure what the error is but my guess is that it has to do with the new support in DBD::mysql 3.0 for prepared statements. I haven't actually tried a reinstall of 2.2.6 since upgrading to DBD::mysql 3.0. The bug <http://bugs.mysql.com/bug.php?id=3D15665> that you identified seems to be a very similar problem with USE and =46LUSH queries, so maybe it affects ALTER TABLE as well, I don't know. If the rest of installation went OK, you can probably work around this by applying the queries in the latest plugins/Search/mysql_prep. You can find that here: <http://cvs.sourceforge.net/viewcvs.py/slashcode/slash/plugins/Search/mysql= _prep?rev=3D1.9&view=3Dmarkup> shane wrote: > The problem is the default table type for the table stories is > MyISAM. However, with MySQL v4.x (and 5.x, so far) you can't do > fulltext indexes on MyISAM tables. You can do them on InnoDB > tables, however. Other way around -- MyISAM supports FULLTEXT, InnoDB does not. Note that I don't think we handled that issue very well in the T_2_5_0_x series until the end of last October. Now InnoDB is the default (which is correct) and the plugin forces the table types to MyISAM when it is installed (also correct). If you use R_2_5_0_74 it'll be wonky. OK, so I lied, use T_2_5_0_88 or later. We really should make another R_ tag... --=20 Jamie McCarthy http://mccarthy.vg/ ja...@mc... |