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 South, the project did not use
any migrations at all before.

However, in its very beginnings, it started with a legacy database that
was used with a PHP application that many years ago was replaced with
this Django project.

> 1. Make sure the database schema defined by your models (and Django migrations) exactly matches the one in the database (this includes null constraints, indexes, etc.) to prevent errors in the future

If this is the problem, I'm not sure how to figure out what the
differences actually are, or what mismatch it is that brings the
`migrate` command to abort. Can I somehow have Django provide more
details on the matter?

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 emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/54CFF9FA.4080101%40cafu.de.
For more options, visit https://groups.google.com/d/optout.