You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Aim structures storage should be sqlite, but for production deployment we need a more stable database like MySQL or Postgresql etc. As Aim already uses SQLAlchemy we tried to configure for MySQL, but some of the column type with unique constraint is not supported.
The major was with name and hash uses Text column type with UniqueConstraint, but MySQL doesn't support unique constraint on Text column type. Is it possible to change from Text to Varchar.
Above changes are required is many tables. It was very changes for us as we were starting from scratch, but I'm not sure how to change column type part of migration so we can move our changes to upstream.
Looking forward to discuss the options..
Motivation
Pitch
Alternatives
Additional context
The text was updated successfully, but these errors were encountered:
馃殌 Feature
Currently Aim structures storage should be
sqlite
, but for production deployment we need a more stable database like MySQL or Postgresql etc. As Aim already uses SQLAlchemy we tried to configure for MySQL, but some of the column type with unique constraint is not supported.The major was with
name
andhash
usesText
column type withUniqueConstraint
, but MySQL doesn't support unique constraint onText
column type. Is it possible to change fromText
toVarchar
.Above changes are required is many tables. It was very changes for us as we were starting from scratch, but I'm not sure how to change column type part of migration so we can move our changes to upstream.
Looking forward to discuss the options..
Motivation
Pitch
Alternatives
Additional context
The text was updated successfully, but these errors were encountered: