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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolution for Issue #1, added SQLAlchemy ORM dialect types for MySQL #2

Merged
merged 2 commits into from May 28, 2015

Conversation

rmackinnon
Copy link
Contributor

Found that convert.py was missing the correct stitching for SQLAlchemy ORM dialect for MySQL column types. Added as pull request per @sloria.

Cheers!

@sloria
Copy link
Member

sloria commented May 26, 2015

Thanks @rmackinnon . The Travis build is failing due to flake8 errors. Please uses 4 spaces rather than tabs for indentation. Would you mind making that change?

@rmackinnon
Copy link
Contributor Author

This is what I get for using nano for a quick edit instead of PyCharm like I do for everything else.... sigh

Pulled into to PyCharm, and sure enough the columns were no where correct. Re-aligned per PEP8.

mysql.LONGBLOB: fields.String,

mysql.SET: fields.List,
mysql.ENUM: fields.Enum
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Enum field is now deprecated in favor of using the validate.OneOf validator. I will change this to fields.Field when I merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants