Schema support is this 12 year old ticket:
https://code.djangoproject.com/ticket/6148
On Sun, 16 Feb 2020 at 20:02, Matt del Valle wrote:
> EDIT:
>
> Actually, after some further digging it turns out it's worse than I
> thought. Unless I'm missing something it looks like there currently isn't
>
EDIT:
Actually, after some further digging it turns out it's worse than I
thought. Unless I'm missing something it looks like there currently isn't
any non-hacky way at all to set a table's schema in django. There are
workarounds that involve SQL escaping hacks such as setting a model's
db_na
Hi,
So currently django seems to take the name of your models (either inferring
it from the model class name or, if provided, it takes it from the model
Meta options), and prepends the name of the app the model belongs to with
an underscore to avoid table name conflicts. It then creates that t
Please read this in full - you will not be disappointed by the end.
We often talk about "multiple-inheritance" when referring to multiple
levels of {% extends ... %} and defining {% block ... %} many layers up in
base templates.
But, something that comes up as a useful idea in my mind on a regu
