Serendipity Forums

I have to come back to this issue.
New Mysql Server 5.5.5x versions come with InnoDB as the default storage engine, AFAIK... but Serendipity needs MyIsam, at least for things like CREATE FULLTEXT INDEX. Its not that easy to switch back in general in the my.cnf... or convert the databases or tables on the fly... So it might be good to check and note this strongly before install, wouldn't it?

But MyISAM is still available? If so, then set the tables that need MyISAM to MyISAM during installation.

Yes it is available.
Well, I did not ask this on my behalf, as I can do this on my own by ALTER..., script or similar, but there may be usage scenarios, where this hits users not being advanced enough to know and do this on their own? We already had some threads here claiming the fulltext index, because of this in the past.

To set MyISAM during installation sounds good - that is why I asked here. Maybe we could use the simple rule: SET storage_engine=MYISAM; and add that easily to the DB.sql...?!

....and maybe a check if MyISAM is available before the installation starts. Isn't there already a check page at the beginning of the installation?

This only checks if a mysql db is available and usable, not which storage engine is set, I assume.

If you check this, you can also check if MyISAM is available. Better to check at the beginning than stop with an error later.

That is exactly the point why I asked.

Maybe there were issues not to have this before, or we have it already and it doesn't work on my local environment, etc etc etc ... maybe there is no need, as hosting services always set MyISAM as default... etc... I don't know.

Hi!

IMHO the best idea is in MySQL layers to enable "SET .. = myisam". MyISAM is there to stay at leasts for a couple of revisions, so I don't think we need to currently go through the extra trouble of adding user options whether to use myisam or innodb, or whatever...?

Regards,
Garvin

Yepp, true!
Would you please do this? Having this would be great!

Hi!

Done. I added it to the schema_import option, which should be the only place we create tables and indexes; so the SQL statement is not sent to the server when no create statement was issued...please report any issues you might find with that approach.

Regards,
Garvin

works like a charm! (Even in 1.6)
Thank you.