Skip to content

Autoincrement for mariadb causes problems with Query Language

Created by: Quazgar

Dirty fix in patch 2.0.31 of the mysql database scheme:

Inserts a new dummy entry into the entity table in order to circumvent some

compatibility problems with old mariadb versions (below 10.2.4).

See: https://mariadb.com/kb/en/library/auto_increment/#setting-or-changing-the-auto_increment-value

Update mysql schema to version v2.0.31

Imported comments:

By Timm Fitschen on 2019-09-02T07:32:09.496Z

closed

By Henrik tom Wörden on 2019-08-30T10:52:14.948Z

unassigned @henrik_indiscale

By Henrik tom Wörden on 2019-08-30T10:52:08.708Z

For me too

By Quazgar on 2019-08-30T08:38:06.024Z

Seems OK for me.

By Timm Fitschen on 2019-08-29T09:25:10.670Z

changed due date to September 04, 2019

By Timm Fitschen on 2019-08-29T09:24:56.978Z

assigned to @quazgar and @henrik_indiscale

By Timm Fitschen on 2019-08-29T09:24:00.169Z

There exists a dirty fix. The initial problem will disappear as soon as we implement UUID Entity IDs.

So we should probably leave this as it is and consider it fixed.

By Quazgar on 2019-08-13T09:25:55.378Z

assigned to @timm.fitschen and unassigned @quazgar

By Quazgar on 2019-01-03T09:29:30.179Z

@tfitsch Is this still valied or already fixed?

By Alexander Schlemmer on 2019-01-03T09:29:30 (imported from GitLab project)

By Quazgar on 2018-11-19T16:24:42.773Z

mentioned in commit 981018eb

By Timm Fitschen on 2018-11-19T16:24:42 (imported from GitLab project)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information