Closed GoogleCodeExporter closed 9 years ago
Sorry I made a small mistake there. Take note that the error is surrounding the
SubSection class in:
parent_subsection = models.ForeignKey('SubSection', null=True, blank=True)
This will produce the same error if 'self' is used (which is recommended in the
docs)
parent_subsection = models.ForeignKey('self', null=True, blank=True)
Original comment by mi...@sturge.ca
on 8 Mar 2011 at 6:32
Could you please check this with a new database.
Is any error comes at the 1st run of reset command also?
Please provide me the db2level of DB2, and the system information like on which
platform your application is running and database resides on which platform.
Original comment by rahul.pr...@in.ibm.com
on 14 Mar 2011 at 4:57
I have tried to reproduce it on Linux and Window, but for these platform
"reset" goes fine for your specified models.
Currently i didn't have AIX machine so, i haven't check it on AIX. Once i get
AIX machine i will try on it also.
By looking into ERROR message, it looks like
"PARENT_SUBSECTION_ID_REFS_ID_D67070D" FKey constraint didn't present on your
existing "PARENT_SUBSECTION" table.
It may happens due to some silent error occurs, when you first time issued
"reset" command and due to this "PARENT_SUBSECTION_ID_REFS_ID_D67070D" haven't
created.
Please check the availability of this constraint.
If possible then try to run it on Linux/Window and let us know about error
message.
Thanks,
Rahul Priyadarshi
Original comment by rahul.pr...@in.ibm.com
on 14 Mar 2011 at 12:08
I also tried to reproduce it on AIX, but i didn't get any error.
Please let me know if you are still getting the error or, is it already
resolved.
Original comment by rahul.pr...@in.ibm.com
on 16 Mar 2011 at 10:09
I found that manually deleting the tables in question resolved the issue for
me. So running a "DROP TABLE <TABLENAME>" on each table in the model. Then
running "python manage.py syncdb" to create them again.
This is a strange error that is not reproducible 100% of the time, but when I
get it now at least I have a workaround
Original comment by mi...@sturge.ca
on 16 Mar 2011 at 11:32
Original comment by rahul.pr...@in.ibm.com
on 23 Mar 2011 at 12:34
Original issue reported on code.google.com by
mi...@sturge.ca
on 8 Mar 2011 at 6:29