Is this normal behavior for propel?
I have a mySQL table with some fields defined. At the moment the table is not populated (though this problems occurs even with tables that are already populated).
My propel:build-schema command fails with a table when it hits a field that is defined to NOT ALLOW NULLS (i.e. default set to NOT NULL). To me, this is normal safe practice from the database point of view when a field is REQUIRED.
In order to prevent propel:build-schema from failing, I have to redefine the offending field(s) to ALLOW NULLS (i.e. default set to NULL). This goes against my grain... what if some admin person needs to hand-enter some records? Without the safeguard of the NOT NULL definition, the admin guy/gal could skip the field and dirty up my data!!!
I appreciate that Symfony has/uses data validation techniques but the world does not yet run entirely from within Symfony and dirty data can be a nightmare to resolve.
Forgive me if I posted this report for the wrong Ticket Property (Component)!
