Hi Markus, I was thinking same.
On Sat, 3 Sep 2022, 14:02 Markus Holtermann,
wrote:
> This is expected and by design. Because in the model where you define the
> foreign key, you also don't define its type. The type is automatically
> resolved through the column type from the target model.
>
> C
This is expected and by design. Because in the model where you define the
foreign key, you also don't define its type. The type is automatically resolved
through the column type from the target model.
Cheers
Markus
On Fri, Sep 2, 2022, at 10:39 AM, Manasvi Dobariya wrote:
> I have default prim
I guess it might be changed by postgres. Have you checked postgres
documentation ?
On Fri, 2 Sep 2022, 18:45 Manasvi Dobariya, wrote:
> I have default primary key in the model which is being referenced as
> foreign key in another model. Now, when I change this primary key type from
> AutoField t
I have default primary key in the model which is being referenced as
foreign key in another model. Now, when I change this primary key type from
AutoField to BigAutoField, migrations for only primary keys are being
generated no migration for foreign key is generated. However, when I apply
the m
4 matches
Mail list logo