Re: default values on database level
W dniu czwartek, 29 marca 2018 19:28:39 UTC+2 użytkownik Michael Grijalva napisał: > > Yeah seems like `db_default` was the felling, at least last time I scanned > through this long-going discussion :D > > I've had to tweak Django's migration handling a bit to handle our > zero-downtime requirements. > This is not the only one issue with Django migrations. -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/286135f8-8407-4964-8ebe-047cdddcf0c3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Get decorator
Hi community, I always want to ask if it's not a god idea change some get_ methods with the property decorator? Things like get_absolute_url for example. What are your thoughts about that? -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/b4d4dd2f-eaaa-4758-aa3a-22eade759fc8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Simplify middlewares (again) and get rid of process_view
Hi Carl, On Wednesday, May 16, 2018 at 5:58:02 AM UTC+2, Carl Meyer wrote: > > I'm not sure this part is feasible. It's an intentional part of > middleware design AFAIK (and useful) that middleware can modify > request.path and have this modification respected in view resolution. > my proposed urlresolver_factory takes the request as argument and should therefore allow for anything that the middleware would allow too -- are there any specific usecases you have in mind that would require a middleware? -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/3f216c46-c48d-4ff1-bd6a-dcc2fb090c43%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
