Thank you for all replies.
@James
Your proposal about design change is generally OK, but while doing the
upgrade I definitely DO NOT want to change the implementation. It is just
too risky.
@Tim
Sorry for hostile sounding, but I'm just tired of such drastic changes. For
a x-years long project it is a quite big issue.
The most important thing is not to destroy the data and to have a security
patches applied. The rest should remain untouched.
The big problem with Django lies somewhere in between - to get recent
patches you must accept whole set of changes, incl. breaking compat ones.
I'm considering upgrade just because 1.8 is not supported AND it has some
serious drawbacks (here -- automatic removal of contenttypes).
Where I am doing one step forward, the upgrade takes me "two" steps back.
I was quite happy when more freedom was left to the developer. It was from
v0.96 up to v1.4.
The things started getting "worse" when builtin migrations and system
checks framework were introduced.
And the "worse" word is very subjective here.
Anyway, thank you for a quick response and hint about changing auto_now_add
to the `default` attr.
Marcin
--
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+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/90a293a8-bcf6-4d51-bd1e-5f87ffa83f95%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
