On Jun 2, 3:57 am, Russell Keith-Magee
wrote:
>
> For auditing purposes, a ticket is always helpful, even if the ticket
> is closed straight away. That way, anyone who hits the same problem
> later on can see the source of the problem and the fact that a
> solution should be coming in the near fu
On Sat, Jun 2, 2012 at 5:39 AM, Ian Kelly wrote:
> On Fri, Jun 1, 2012 at 12:29 PM, Vinay Sajip wrote:
>>
>> On Jun 1, 6:39 pm, Ian Kelly wrote:
>>>
>>> The error is caused by one of the column names in the table. See the
>>> second paragraph at:
>>>
>>> https://docs.djangoproject.com/en/1.4/re
On Fri, Jun 1, 2012 at 12:29 PM, Vinay Sajip wrote:
>
> On Jun 1, 6:39 pm, Ian Kelly wrote:
>>
>> The error is caused by one of the column names in the table. See the
>> second paragraph at:
>>
>> https://docs.djangoproject.com/en/1.4/ref/databases/#naming-issues
>>
>
> Thanks, that helped. It s
On Jun 1, 6:39 pm, Ian Kelly wrote:
>
> The error is caused by one of the column names in the table. See the
> second paragraph at:
>
> https://docs.djangoproject.com/en/1.4/ref/databases/#naming-issues
>
Thanks, that helped. It seems that in this case, the offending name is
'date'. I added a d
On Fri, Jun 1, 2012 at 11:29 AM, Vinay Sajip wrote:
> I'm getting an error when syncdb tries to execute the following SQL
> against Oracle 10g XE:
>
> CREATE OR REPLACE TRIGGER "ADMIN_CHANGELIST_EVENT_TR"
> BEFORE INSERT ON "ADMIN_CHANGELIST_EVENT"
> FOR EACH ROW
> WHEN (new."ID" IS NULL)
> BEG
I'm getting an error when syncdb tries to execute the following SQL
against Oracle 10g XE:
CREATE OR REPLACE TRIGGER "ADMIN_CHANGELIST_EVENT_TR"
BEFORE INSERT ON "ADMIN_CHANGELIST_EVENT"
FOR EACH ROW
WHEN (new."ID" IS NULL)
BEGIN
SELECT "ADMIN_CHANGELIST_EVENT_SQ".nextval
INTO
