Hi, On Saturday 09 January 2016 18:29:32 Shai Berger wrote: > The other is migrations which *create* data -- fill in tables for > database- implemented-enums, for example. If you remove these, you are > going to break your tests (if you do this and haven't broken your tests, > your tests are missing -- I'd go as far as calling them broken).
I agree with Carl. I avoid Django migrations for this kind of data. Obviously, you don't get dependency handling that way, but I think this is typically not a problem for this kind of data. I wonder if this approach should actually be an official recommendation. -- René Fleschenberg -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/1856941.AoUJGOvPjS%40rex. For more options, visit https://groups.google.com/d/optout.
