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 some subtle issues
from the export-import cycle are responsible for the ORA-00955 on my
developer machine, and so I'll just give it a try.
Also, I suspect that if not for the ORA-00955 error, the initial
migrations for this app would turn out to be "FAKE" applied -- just as
was the case with other previously unmigrated apps that I successfully
added initial migrations to after the upgrade to Django 1.7.
However, I don't quite dare yet running
./manage.py migrate --fake
explicitly, mostly because I'm not sure how to undo or recover if there
are subsequent problems, or if there is a way to re-try, etc.
(On the other hand, if this worked and there were errors only much
later, they would probably occur after individual, small changes, thus
much smaller migration files, and thus (I recon) much easier to pin down
as from the big stack trace about the ORA-00955...)
Any help or hint would still be very much appreciated.
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+unsubscr...@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/54E74A42.4010703%40cafu.de.
For more options, visit https://groups.google.com/d/optout.
