Re: [Slashcode-general] SQL error in install-slashsite: "This command is not supported in the prepared statement protocol yet"

[Jamie M. <ja...@mc...>]

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...