Re: one patch to fix a Django 1.8 issue for merging legacy database

2015-04-28 Thread Shai Berger
Hi Ben, Thanks for the change you suggested. On Tuesday 28 April 2015 09:48:26 Ben L wrote: >[paraphrase] An automatic primary key shouldn't be added to unmanaged models, >[paraphrase] the current behavior where it is added is a bug Please have a look at the documentation[1] -- it states clearl

Re: one patch to fix a Django 1.8 issue for merging legacy database

2015-04-28 Thread Marc Tamlyn
The automatic ID field would not be added if you have a primary key. I'm not sure if inspectdb does pick up primary keys, I believe it does though. I feel this discussion may be more suited to django-users, our forum for helping debugging user issues. Marc On 28 April 2015 at 07:48, Ben L wrote

one patch to fix a Django 1.8 issue for merging legacy database

2015-04-28 Thread Ben L
Issue: I have an existing database, so the guide in https://docs.djangoproject.com/en/1.8/howto/legacy-databases/ to inspect db and created models.py . That table does NOT have an 'id' column, and the created models.py doesn't have 'id' either, and the class is unmanaged (managed=False). But w