Comment (by la_iscla@…):
I'm experiencing the same issue here. Annoying. Any chance to see this
fixed?
--
Ticket URL: <https://code.djangoproject.com/ticket/14096#comment:9>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Comment (by timo):
Update the patch and add a test if you'd like to get it fixed.
--
Ticket URL: <https://code.djangoproject.com/ticket/14096#comment:10>
Comment (by la_iscla@…):
Well, I've made a workaround with Postgres by having the model tables rely
on the same SEQUENCE counter:
ALTER TABLE mymodule_a ALTER COLUMN id SET DEFAULT
nextval('mymodule_c_id_seq');
I'll dig further into this issue whenever I have more time.
--
Ticket URL: <https://code.djangoproject.com/ticket/14096#comment:11>
* status: new => closed
* resolution: => invalid
Comment:
Closing as invalid given the provided models don't validate:
{{{
data.Company: (models.E005) The field 'id' from parent model
'data.account' clashes with the field 'id' from parent model
'data.contact'.
data.Employee.company: (models.E006) The field 'company' clashes with the
field 'company' from model 'data.contact'.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/14096#comment:12>