Optional or required is not the same thing as important. It is entirely valid to have important but optional fields on a model.
For example, a field that contains a string reference to a python callback function that modifies the behaviour of some model methods when set. We use this on a Broadcast model in a mailing list application. The callback is used to generate additional context for the email template for personalisation when sending out email newsletters. This is important data that should not be lost as it will change the behaviour of model methods (in this case, potentially sending the same email newsletter without personalisation to many recipients), but it may not be required for every instance of the model. Cheers. Tai. On Jan 12, 1:11 am, Babatunde Akinyanmi <tundeba...@gmail.com> wrote: > -1 > I think a programmer should not specify a field that would contain > important data as optional in the first place. If the data loss from > not including it in the form is going to cause problems then it should > not be optional. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
