On Jul 3, 3:23 pm, El Marto <[EMAIL PROTECTED]> wrote:
> Hi all!
>
> I've developed and tested an application in MySQL and everything
> worked fine fine fine. Now i am migrating to Oracle, the app works
> fine but I am having a lot of trouble with the Django admin.
>
> Whenever i run syncdb, it creates one table and throws an exception
> like this:
>
> ORA-00955: name is already used by an existing object
>
> Luckily every time I run it, it creates another table and crashes. So
> by running the syncdb command SEVERAL times, I get all the tables.
> (this should all be a sign that something is not working ok with
> oracle). But this is not the problem. When the tables are complete, I
> run it again and i get
>
> ORA-01400: cannot insert NULL into
> ("ORACLE"."DJANGO_CONTENT_TYPE"."ID")
>
> and i dont seem to have a workaround for this.
>
> What can i do? please please please help me :DIt sounds like what's happening is that for each table, it succeeds in creating the table, but then fails to create the corresponding sequence, because the name is already in use. Since it raises an error at the sequence, the AutoField trigger doesn't get created either, and so you get the second error when trying to save objects. Did you perhaps create the schema once before, but then dropped all the tables without also dropping the sequences? Try clearing out the schema entirely and then running syncdb again. Ian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
