Maybe because there is a high change that you will try to find rows based on this SlugField, so in common cases this INDEX will be nice.
Also it's documented on http://www.djangoproject.com/documentation/model-api/#slugfield that this field has an implicit db_index=True, BUT you can always pass db_index=False if you do not want the index. Cheers, Marc On 4/13/07, xav4django <[EMAIL PROTECTED]> wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Hi. > > When I use a SlugField in a model, > an index for this field is create in postgres. > > Why ? > > (config : django 0.96 / postgresql ) > > A++ Xav. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFGH2rD4dg3EDuiPUcRAgmZAJ9qSsRXPZALQ51L0eX67EtAivxl3wCfQARH > /lI6QD8Rxn9MXU5LPfAvxiM= > =+Ssi > -----END PGP SIGNATURE----- > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
