#17015: IntegrityError: ORA-01400: cannot insert NULL into
(...."AUTH_PERMISSION"."ID") when running syncdb with Oracle
-------------------------------------+-------------------------------------
Reporter: anonymous | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.3
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: oracle, trigger | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by anonymous):
* keywords: => oracle, trigger
Comment:
Replying to [comment:4 ikelly]:
> Sounds to me like the sequence trigger is missing for some reason. Can
you verify whether the TEST1.AUTH_PERMISSION table has any triggers on it?
You are right, I checked the "AUTH_PERMISSION" table and it does not have
a trigger.
On other instances that work with oracle, the trigger "AUTH_PERMISSION_TR"
exists.
I did the following to resolve this issue.
drop table AUTH_PERMISSION; grant trigger to TEST1; python manage.py
syncdb;
I didn't get the error anymore and verified the trigger was created.
It seems that on the initial syncdb it was able to create all objects
except triggers because it didn't have that permission.
Shouldn't the syncdb catch the permissions error for triggers like it does
on sequence?
--
Ticket URL: <https://code.djangoproject.com/ticket/17015#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
