Message from discussion
Syncdb Error With Oracle Database - IntegrityError Exception
Received: by 10.236.179.9 with SMTP id g9mr5559634yhm.30.1346426649240;
Fri, 31 Aug 2012 08:24:09 -0700 (PDT)
X-BeenThere: django-users@googlegroups.com
Received: by 10.236.78.164 with SMTP id g24ls5130678yhe.6.gmail; Fri, 31 Aug
2012 08:23:29 -0700 (PDT)
Received: by 10.236.87.71 with SMTP id x47mr885314yhe.6.1346426609428;
Fri, 31 Aug 2012 08:23:29 -0700 (PDT)
Date: Fri, 31 Aug 2012 08:23:28 -0700 (PDT)
From: Ian <ian.g.ke...@gmail.com>
To: django-users@googlegroups.com
Message-Id: <584765c3-03d2-413f-96fb-b4733b54adfd@googlegroups.com>
In-Reply-To: <CAA60zMM6H29dZ-4NxLE23wBOWc0OE--wKiaeJC39NUmL4BeJbw@mail.gmail.com>
References: <a4569558-3512-4eae-8cc3-291f267dad2f@googlegroups.com>
<CAA60zMM6H29dZ-4NxLE23wBOWc0OE--wKiaeJC39NUmL4BeJbw@mail.gmail.com>
Subject: Re: Syncdb Error With Oracle Database - IntegrityError Exception
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_430_22751291.1346426608776"
------=_Part_430_22751291.1346426608776
Content-Type: multipart/alternative;
boundary="----=_Part_431_7103973.1346426608776"
------=_Part_431_7103973.1346426608776
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
On Friday, August 31, 2012 12:10:54 AM UTC-6, Amyth wrote:
>
> Hey Jon,
>
> I guess this is because of a bug in django. Django already has a open
> ticket for this bug. Check it out here<https://code.djangoproject.com/ticket/17015>
> .
>
>
As described in that ticket, the reason for the problem is probably just
that the Django user does not have the CREATE TRIGGER privilege, which it
needs. The bug in Django is just that this condition is not detected and
reported at the time the table is created, instead of getting a rather more
obscure error message at the time the table is populated.
------=_Part_431_7103973.1346426608776
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
On Friday, August 31, 2012 12:10:54 AM UTC-6, Amyth wrote:<blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">Hey Jon,<div><br></div><div>I guess this is because of a bug in django. Django already has a open ticket for this bug. Check it out <a href="https://code.djangoproject.com/ticket/17015" target="_blank">here</a>. <br><br></div></blockquote><div><br>As described in that ticket, the reason for the problem is probably just that the Django user does not have the CREATE TRIGGER privilege, which it needs. The bug in Django is just that this condition is not detected and reported at the time the table is created, instead of getting a rather more obscure error message at the time the table is populated.<br></div>
------=_Part_431_7103973.1346426608776--
------=_Part_430_22751291.1346426608776--