My first idea when I saw this thread was, that maybe the NULL is the default and so nothing is submitted there (which would be wrong). In the meantime you'll just have to manually add NULL to the ALTER-command. Or, if there is no data in the database yet, then first delete the field and add it again after that, in two steps.
The warning you mention on PHP5.4 seems to me another thing (no idea what). You'd have to test some more to find where that warning is coming from. On Wednesday, 19 March 2014 10:16:09 UTC+1, Herman Peeren wrote: > > It *should *not be, but it certainly *could *be a bug. > The way to know certain is to provide a good test. If it indeed is a bug, > then add the issue (with test) to the tracker. > > On Tuesday, 18 March 2014 22:44:51 UTC+1, Parsifal wrote: >> >> In an entity I did change a field nullable from false to true >> and run the command to update schema, in output I see: >> >> ALTER TABLE tablename CHANGE fieldname fieldname VARCHAR(255) DEFAULT '', >> CHANGE fieldname1 fieldname1 VARCHAR(255) DEFAULT ''; >> >> It changed from what to what??? the fieldname and fieldname1 in db are >> still NOT NULL! why they weren't changed to NULL? >> >> and as php 5.4 I get this: >> Warning: PDO::__construct(): The server requested authentication method >> unknown to the client [mysql_old_password] in >> /vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php on line 40 >> >> I doctrine compatible with php 5.4? >> >> >> > -- You received this message because you are subscribed to the Google Groups "doctrine-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/doctrine-user. For more options, visit https://groups.google.com/d/optout.
