Running ./symfony madb:init fails
Closed this issue · 5 comments
Author Name: Yann Le Doaré (Yann Le Doaré)
Original Redmine Issue: 112, http://mageia-app-db.tuxette.fr/issues/112
Original Date: 2011/02/03
Original Assignee: Adrien Gallou
I had to change
$script .= "Type=$mysqlTableType";
with
$script .= "ENGINE=$mysqlTableType";
into lib/vendor/symfony/lib/plugins/sfPropelPlugin/lib/vendor/propel-generator/classes/propel/engine/builder/sql/mysql/MysqlDDLBuilder.php
to make it working with my Mysql (5.5.8)
Original Redmine Comment
Author Name: Yann Le Doaré (Yann Le Doaré)
Original Date: 2011/02/03 19:05:47 +0100
more info here : http://bugs.mysql.com/bug.php?id=17501
Original Redmine Comment
Author Name: Adrien Gallou (@agallou)
Original Date: 2011/02/03 21:57:33 +0100
there may be a solution to this issue. That's to add the tableEngineKeyword in the config/propel.ini file :
propel.mysql.tableEngineKeyword = ENGINE
but it apears that this property works only on propel 1.5.
so the solution may be to update propel to the 1.5 version.
Original Redmine Comment
Author Name: Samuel Verschelde (@stormi)
Original Date: 2011/02/10 23:42:51 +0100
Adrien, will switching to a newer version of propel risk delaying the 0.2 release ? (In which case I vote for changing milestone to 0.3)
Original Redmine Comment
Author Name: Yann Le Doaré (Yann Le Doaré)
Original Date: 2011/03/23 15:23:15 +0100
The fix
Original Redmine Comment
Author Name: Samuel Verschelde (@stormi)
Original Date: 2011/04/08 21:09:08 +0200
This bug will prevent madb from running on mageia, so we must fix it before release.
We've got 2 options :
- use Yann's "dirty" fix (dirty because it involves touching to propel's code), as a temporary solution until we switch to propel's next version
- switch to propel 1.5 sooner than expected