Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

SQLAlchemy support for MySQL #3072

Open
sharathmk9 opened this issue Dec 26, 2023 · 0 comments
Open

SQLAlchemy support for MySQL #3072

sharathmk9 opened this issue Dec 26, 2023 · 0 comments
Labels
type / enhancement Issue type: new feature or request

Comments

@sharathmk9
Copy link

sharathmk9 commented Dec 26, 2023

馃殌 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 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.

sa.Column('uuid', sa.VARCHAR(512), nullable=True),
sa.Column('name', sa.VARCHAR(512), nullable=False),

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

@sharathmk9 sharathmk9 added the type / enhancement Issue type: new feature or request label Dec 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type / enhancement Issue type: new feature or request
Projects
None yet
Development

No branches or pull requests

1 participant