manage.py sqlindexes does not create the index for unique_together fields

[litnimax]

Pls see example below:

Model:

class SpeedDial(models.Model):

    account = models.ForeignKey(VoipAccount, editable=False)
    sequence = models.CharField(maxlength=1)
    number = models.CharField(maxlength=20)

    def __str__(self):
        return '%s' % self.sequence

    class Admin:
        list_display = ('sequence', 'number')
        list_display_links = ('sequence', 'number')

    class Meta:
        ordering = ('sequence', )
        unique_together = (('sequence','account'),)        

max@explorer ~/Development/public/dtl/r_manager/trunk/rmanager $ python manage.py  sqlall pbx
BEGIN;
CREATE TABLE `pbx_speeddial` (
    `id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY,
    `account_id` integer NOT NULL REFERENCES `ENTVOIPACCT` (`ATRACCTID`),
    `sequence` varchar(1) NOT NULL,
    `number` varchar(20) NOT NULL,
    UNIQUE (`sequence`, `account_id`)
);
CREATE INDEX `pbx_speeddial_account_id` ON `pbx_speeddial` (`account_id`);
COMMIT;

But when we issue:

max@explorer ~/Development/public/dtl/r_manager/trunk/rmanager $ python manage.py  sqlindexes pbx
CREATE INDEX `pbx_speeddial_account_id` ON `pbx_speeddial` (`account_id`);

it only generates index for foreign key.

What about uniq index!?

[Simon G. <dev@…>]

Confirmed as of r5798

[Eratothene]

It looks like the unique contraint also causes the index to disappear.

Example:
class A(models.Model):

    a = models.CharField(maxlength=1, unique=True, db_index=True)

Should be: CREATE UNIQUE INDEX
instead no index, just unique constraint

[Renato Alves]

If your backend is MySQL (I don't about other backends), UNIQUE and PRIMARY KEY columns are automatically (internally) indexed.

You don't need to explicitly add other indexes to the same columns.

Also from a construction point of view, UNIQUE is not a standard INDEX as it will fail if the column in question has non unique content. Therefore from my point of view, it should be part of the CREATE TABLE and not of CREATE INDEX statements.

In summary, the original decision is supported by the same reasons that made syncdb not to issue ALTER TABLE statements.

[Aymeric Augustin]

Change UI/UX from NULL to False.

[Aymeric Augustin]

Change Easy pickings from NULL to False.

[Anssi Kääriäinen]

Why should sqlindexes produce CREATE UNIQUE INDEX command? It is an implementation detail of the DB how it enforces the unique index. As far as I know, every supported database automatically creates an unique index to enforce the constraint, but there is no reason why Django should do that. In fact, it is probably wrong to produce both CREATE UNIQUE INDEX (a) and UNIQUE(a).

If there is some database where the CREATE UNIQUE INDEX is needed, then that is a clear bug, and needs its own ticket.