I don't have that issue. If I were to change a nullable property, it would also include the alter to that table. I just figure it should be able to detect if the fk already exists, and not drop and re-add.
On Monday, April 21, 2014 2:26:38 PM UTC-6, Parsifal wrote: > > Does this actually affect on your database? For me I too get all these fk > each time on console output but nothing affected on my db actually, e.g. if > I change nullable from true to false or change a blank default to a value > no changes on db at all when running this update. > -- 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.
