Michael van der Westhuizen wrote:
> Hi,
> 
> On 11/17/06, ogghead <[EMAIL PROTECTED]> wrote:
>> The django source code in the boulder-oracle-sprint branch has had the
>> trunk HEAD merged in, and now passes all but 4 of the 65 tests in the
>> suite against my 10g and 9i database instances.
> [snip]
> 
> I've finally got around to getting this checked out and tested.
> 
> The first oddity I ran into is that Oracle does not like two indexes
> on the same table which index the same columns (it's obvious why it
> doesn't like this...). This happens when running manage.py syncdb, and
> fortunately does not stop the syncdb from completing. I've attached my
> models.py in case anybody wants to look into this. The specific
> indexes are:
> 
> Failed to install index for quality.Document model: ORA-01408: such
> column list already indexed
> Failed to install index for quality.Collection model: ORA-01408: such
> column list already indexed
> 

this two-indexes-on-the-same-column thing is also happening with 
postgres . in postgres it's not an error, but still it's not really optimal.

the problematic field is:

> 
> class Collection(models.Model):
>       slug = models.SlugField( unique = True, prepopulate_from = ( 'name', ), 
> help_text = 'Automatically derived from the collection name.' )

(at least in the postgres-problem)

here you have an unique SlugField. a SlugField implies db_index, so:

1. postgres automatically creates an index, because the field is unique
2. afterwards, django also creates an index, because db_index was specified.


ps: of course, it might happen for entirely different reasons in oracle, 
i haven't tested it in oracle.

gabor

--~--~---------~--~----~------------~-------~--~----~
 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?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to