server.selections: specified key was too long; max key length is 1000 bytes

[yomguy]

@AnasGhrab reported:
Parisson/Telemeta#78

Running migrations for django_extensions:

• Nothing to migrate.

  • Loading initial data for django_extensions.
    Installed 0 object(s) from 0 fixture(s)
    Running migrations for telemeta:

• Nothing to migrate.

  • Loading initial data for telemeta.
    Installed 0 object(s) from 0 fixture(s)
    Running migrations for server:
  • Migrating forwards to 0001_initial.

    server:0001_initial
    FATAL ERROR - The following SQL query failed: CREATE TABLE timeside_selections (id integer AUTO_INCREMENT NOT NULL PRIMARY KEY, date_added datetime NOT NULL, date_modified datetime NULL, uuid varchar(512) NOT NULL UNIQUE, title varchar(512) NOT NULL, description longtext NOT NULL, author_id integer NULL)
    The error was: (1071, 'Specified key was too long; max key length is 1000 bytes')
    ! Error found during real run of migration! Aborting.

  ! Since you have a database that does not support running
  ! schema-altering statements in transactions, we have had
  ! to leave it in an interim state between migrations.

! You might be able to recover with: = DROP TABLE timeside_selections CASCADE; []
= DROP TABLE timeside_selections_items CASCADE; []
= DROP TABLE timeside_selections_selections CASCADE; []
= DROP TABLE timeside_items CASCADE; []
= DROP TABLE timeside_experiences CASCADE; []
= DROP TABLE timeside_experiences_presets CASCADE; []
= DROP TABLE timeside_experiences_experiences CASCADE; []
= DROP TABLE timeside_processors CASCADE; []
= DROP TABLE timeside_presets CASCADE; []
= DROP TABLE timeside_results CASCADE; []
= DROP TABLE timeside_tasks CASCADE; []

! The South developers regret this has happened, and would
! like to gently persuade you to consider a slightly
! easier-to-deal-with DBMS (one that supports DDL transactions)
! NOTE: The error which caused the migration to fail is further up.
Error in migration: server:0001_initial

[yomguy]

We should restrict this to 950 bytes fir MyISAM DBs.

[AnasGhrab]

Is there something that I can do now, or do I have to go back to 1.5.2 ?

[yomguy]

just hold on ;)

[yomguy]

weird because selection.title is 512 chars, description is a TextField, moreover it passes the CREM DB which is MyISAM :/
For the moment, as far as timeside.server is experimental, you can remove it from INSTALLED_APPS and it should be OK to use Telemeta..

[thomasfillon]

Hi

From what I can see in some discussions on the web, it may be due to the following field in the Selection model:

uuid = models.CharField(_('uuid'), unique=True, blank=True, max_length=255)

The combination between unique=True and max_length=255 may be the source of the problem.
I wil try to propose a fix for that.

Or maybe this field

   title = models.CharField(_('title'), blank=True, max_length=512)

[thomasfillon]

@AnasGhrab : clould you please try to use this branch of TimeSide with a tentative fix : https://github.com/Parisson/TimeSide/tree/hotfix/issue81

[thomasfillon]

@AnasGhrab: oh sorry, wait a minute, I forgot to squash the migration.

[AnasGhrab]

It was Ok after installing the good version of elasticsearch.

[thomasfillon]

OK thank you very much for the feedback.
I get lost in the migration process ;)