Re: [solved] Migrating to initial migration: "ORA-00955: name is already used by an existing object"

Hi all, it seems like I found the culprit, along with a simple solution: https://code.djangoproject.com/ticket/24407 :-) Best regards, Carsten -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving

Re: Migrating to initial migration: "ORA-00955: name is already used by an existing object"

Hi all, another update: My developer system's local Oracle database content was created from importing a dump of a production database. On Monday night I'll have a chance to safely try to create and apply the initial migrations on the production database, rather than my dev system. Maybe

Re: Migrating to initial migration: "ORA-00955: name is already used by an existing object"

Hi all, Am 02.02.2015 um 22:50 schrieb Carsten Fuchs: It seems that creating the initial migrations with `makemigrations` works well, but the first run of `migrate` aborts with error "django.db.utils.DatabaseError: ORA-00955: name is already used by an existing object". Please see the full

Re: Migrating to initial migration: "ORA-00955: name is already used by an existing object"

Hi Markus, thanks for your reply! Am 02.02.2015 um 22:59 schrieb Markus Holtermann: Did you see the chapter at the end of the page you linked to: Upgrading from South: https://docs.djangoproject.com/en/1.7/topics/migrations/#upgrading-from-south Well, yes, but I'm *not* upgrading from

Re: Migrating to initial migration: "ORA-00955: name is already used by an existing object"

Hey Carsten, Did you see the chapter at the end of the page you linked to: Upgrading from South: https://docs.djangoproject.com/en/1.7/topics/migrations/#upgrading-from-south 1. Make sure the database schema defined by your models (and Django migrations) exactly matches the one in the

Migrating to initial migration: "ORA-00955: name is already used by an existing object"

Dear Django developers, in a Django project that was created pre-1.7, did not use South before, and was recently upgraded to Django 1.7 and is otherwise fine, I'm now trying to convert it to use migrations, following the docs at