Hi Markus,
My proposed solution simply offers a way to opt-in the attribute exclusion
behavior, I didn't mean to solve the whole data migration access to a
particular state issue.
While I see merit in your proposal I cannot understand how it's not also
encouraging people to use it for the wron
Hi all,
While your proposal could solve the repeated creation of migrations due to
dynamic choices, Simon, I don't see how it would solve or prevent the issue
Carl mentioned earlier. Data migrations may need to have the exact choices at
that particular state. Importing the current choices may f
Hi everyone,
Here's just an idea from the top of my head.
What if we exposed a `django.db.migrations.Reference`
that would be a deconstructible proxy to a top level module object.
It would be initialized with a module name string and the referenced
object name as a second argument. We could docum
Hi Andrew and Marcin,
On 07/15/2015 05:10 PM, Andrew Godwin wrote:
> Django persists every single field attribute change, no matter what it
> is - this was a deliberate decision as we didn't want to declare certain
> attributes as "not important for schema" (for example, a subclass of
> ChoiceFiel
Hi Wim,
On 16/07/15 16:51, Wim Feijen wrote:
Hi,
We are experiencing the same problem when a user changes his language.
We are using a post form for that, see: https://roominreturn.nl .
1. What is annoying is that the csrf Forbidden page is a yellow page and
is shown to the end user. We would
Hi,
We are experiencing the same problem when a user changes his language. We
are using a post form for that, see: https://roominreturn.nl .
1. What is annoying is that the csrf Forbidden page is a yellow page and is
shown to the end user. We would never want to confront a visitor with a
yell
On Jul 16, 2015, at 1:16 AM, Federico Capoano
wrote:
> I also don't like the idea of believing django users are too stupid to
> understand that this advice si valid for development only. Generally
> python and django users are intelligent enough to properly read the
> docs and understand what's
Hey Christophe,
On Thu, Jul 16, 2015 at 8:34 AM, Christophe Pettus wrote:
[CUT]
>
> By the way, I would strongly advise *against* *ever* even mentioning fsync =
> off anywhere in the Django documentation; that is such a horribly bad idea in
> 99.95% of real-life situations that steering people
