Ticket created https://code.djangoproject.com/ticket/32653#ticket
Thank you
On Wednesday, April 14, 2021 at 7:35:22 AM UTC-4 Shai Berger wrote:
> Hi,
>
> On Wed, 14 Apr 2021 12:10:56 +0100
> "'Adam Johnson' via Django developers (Contributions to Django
> itself)" wrote:
>
> > Hi
> >
> > This s
Hi,
On Wed, 14 Apr 2021 12:10:56 +0100
"'Adam Johnson' via Django developers (Contributions to Django
itself)" wrote:
> Hi
>
> This seems like a genuine bug, Django should not assume that all
> backends have the same max table name length. Please file a ticket.
>
Right, but it may be a simpl
Hi
This seems like a genuine bug, Django should not assume that all backends
have the same max table name length. Please file a ticket.
You can workaround this right now by defining db_table on your model. You
might need two model classes, sharing details via inheritance, for the
different backen
I have a model with a really long name think
`ThisIsAReallyLongModelNameThatIsAlsoVeryOld`. To complicate things further
I have a Oracle instance without archival data designated connection name
`old` and a new postgres instance with the connection name `default`.
Issue i've found is that if i
