Re: migrate does not store default values in the database

On 10/24/2014 05:32 PM, Carl Meyer wrote:
> Hi Peter,
>
> On 10/24/2014 05:26 PM, Peter Coles wrote:
>> Should I copy this question over to "django-dev" (do they accept posts
>> from non-internal devs)? I've seen people complain in the past about
>> reopening or commenting on closed tickets.
>
> Django core dev here. Yes, the django-developers mailing list is open to
> anyone, and your question is on-topic for it (since it's a question
> about Django's design and possible improvements/changes to it).
>
> And you are right that bringing the question to the mailing list is the
> right approach, not reopening a ticket that has been closed wontfix
> (multiple times).
>
> I would suggest that you carefully read through the full history of
> https://code.djangoproject.com/ticket/470 and make sure you understand
> why it has been closed wontfix, so that you can make an argument for how
> you'd address those problems (e.g. callable default values) in your
> proposed change. That will increase your chances of starting a
> productive discussion on the topic.

For bonus points, you might also search the archives of
django-developers to see if there have been past mailing-list threads on
the topic as well.

Carl

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/544AE216.6010003%40oddbird.net.
For more options, visit https://groups.google.com/d/optout.