I believe it's a bug that's fixed in Django 1.9:
https://github.com/django/django/commit/f37c11eea3cb860112a26f8a65d823842f65b96f
On Monday, September 28, 2015 at 11:12:26 PM UTC-4, Григорий Крамаренко
wrote:
>
> In migrations I need delete constraints before creating table-partitioning.
> But Dj
In migrations I need delete constraints before creating table-partitioning.
But Django generates different constraint names on different servers.
On server 1:
ALTER TABLE "order_autoselect" ADD CONSTRAINT
"order_autoselec_summary_id_1d623f742c26ae09_fk_order_summary_id" FOREIGN
KEY ("summary_id")
2 matches
Mail list logo