Opened 2 years ago

Closed 2 years ago

#33827 closed Uncategorized (invalid)

Use of old MySQL version generate unknown default_storage_engine.

Reported by: rv2931 Owned by: nobody
Component: Database layer (models, ORM) Version: 3.2
Severity: Normal Keywords: Mysql, database, database.backends, storage_engine
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Hi
I meet the error 

(1193, "Unknown system variable 'default_storage_engine'")

because I'm using an old MySQL version that is waiting for storage_engine and not default_storage_engine
I've tried to add storage_engine in configuration but the default_storage_engin is still used, maybe in addition to storage_engine, and so still generate the error

DATABASES:{
    'default':{}
    'mysqldb': {
        'ENGINE': 'django.db.backends.mysql',
        'HOST': '<url>',
        'PORT': '3306',
        'USER': '<user>',
        'PASSWORD': '<password>',
        'NAME': 'bi_entrepot',
        'STORAGE_ENGINE': 'MyISAM',
        'OPTIONS': {
             'init_command': 'SET storage_engine=MyISAM',
        }
    }

I looked for solution but didn't find any way to solve my situation because I have to use this old version of MySQL

Change History (4)

comment:1 by rv2931, 2 years ago

Component: Uncategorized → Database layer (models, ORM)

comment:2 by Mariusz Felisiak, 2 years ago

Resolution: → invalid
Status: new → closed
Summary: Use of old MySQL version generate unknown default_storage_engine but no way to remove/replace parameter by storage_engine → Use of old MySQL version generate unknown default_storage_engine.

default_storage_engine was introduced in MySQL 5.5.3 and Django 4.0+ support MySQL 5.7 and higher.

comment:3 by rv2931, 2 years ago

Resolution: invalid
Status: closed → new
Version: 4.0 → 3.2

I reopen the ticket because the behaviour is the same in Django 3.2.14

comment:4 by Tim Graham, 2 years ago

Resolution: → invalid
Status: new → closed

Django 3.2.x also ​requires MySQL 5.7 or later.

Note: See TracTickets for help on using tickets.
Back to Top