You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since we now use foreign keys, we need to be explicit about wanting tables to be created using the InnoDB engine. MySQL can default to MyISAM in some circumstances, causing errors like this.
Probably the best approach is to set engine in the database config that's passed to Laravel. We probably wouldn't want this in config.php though. Alternatively we could just set the engine in the migrations where we create tables?
The text was updated successfully, but these errors were encountered:
Setting engine in the DB config works for new installations. For old ones, we'll have to add a new migration that converts to InnoDB if necessary. Agreed?
Re-reading the linked discussion, we will probably not need a migration, as the error happened during fresh installation, and simply running the beta.7 -> beta.8 migrations already won't work.
So I am closing this.
If somebody has a beta.7 forum with MyISAM tables, they will have to manually change the engine to InnoDB prior to upgrading.
Since we now use foreign keys, we need to be explicit about wanting tables to be created using the InnoDB engine. MySQL can default to MyISAM in some circumstances, causing errors like this.
Probably the best approach is to set
engine
in the database config that's passed to Laravel. We probably wouldn't want this inconfig.php
though. Alternatively we could just set theengine
in the migrations where we create tables?The text was updated successfully, but these errors were encountered: