On Tue, 2006-09-19 at 02:22 -0700, world_domination_kites wrote:
[...]
> and i got past that bit. While that's nasty, I at least now know that I
> have to deal with two more accursed Oracle problems and a bug:
>  - no serial/autoincrementing type, sequence + trigger required.

Using Oracle-specific initial SQL will be a workaround to get past that
for the moment (see
http://www.djangoproject.com/documentation/model_api/#database-backend-specific-sql-data
 ). 

A more general solution should be possible, too, but will need a bit of
a redesign in management.py the backend creation.py files. Some kind of
hint being passed back that the field we are about to insert needs
fix-up work later and then post-creation call to the backend, for
example.

>  - it's not OK to use 'long' for 'TextField', a table can only have one
> 'long' column - CLOBs required, kludging with varchar(4000) for the
> moment

Somebody brought that up a while ago. That's a really bad Oracle-ism.

It's going to take a bit of creativity to come up with a nice solution
there.

>  - why is syncdb trying (and failing) to create tables that already
> exist?

It sounds like _get_table_list() in management.py is not returning the
right information. That method is called to work out which tables have
already been installed so that they can be skipped. It calls a
backend-specific function to do the heavy lifting. That would be a good
first stop for debugging prints, I guess.

Sounds like you're making progress, at any rate. All this information is
useful to know about so that changes to management.py, etc, can at least
make it easier for the Oracle experts to do their stuff.

Regards,
Malcolm



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers
-~----------~----~----~----~------~----~------~--~---

Reply via email to