-
Notifications
You must be signed in to change notification settings - Fork 239
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
There is an issue for MySQL Support and SQLAlchemy datadefinitions #359
Milestone
Comments
Thanks @mayday6971 - good timing, this will be included in the upcoming next week's release! |
This is fixed as of 816e3d1 and will be included in Zato 2.0.0. Again, many thanks for spotting and reporting it! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When zato 2.0 is installed and the database is MySQL,the zato create odb command returns an exception.
InternalError: (InternalError) (1074, u"Column length too big for column 'query' (max = 65535); use BLOB or TEXT instead") '\nCREATE TABLE notif_sql (\n\tid INTEGER NOT NULL, \n\tquery VARCHAR(200000) NOT NULL, \n\tdef_id INTEGER NOT NULL, \n\tPRIMARY KEY (id, def_id), \n\tFOREIGN KEY(id) REFERENCES notif (id), \n\tFOREIGN KEY(def_id) REFERENCES sql_pool (id)\n)\n\n' ()
The command I was running:
zato create odb --verbose --store-config --odb_host localhost --odb_port 3306 --odb_user zato --odb_db_name zato --odb_password=zato mysql
To fix this, I had to edit:
/code/zato-common/src/zato/common/odb/model.py
I added a new SQLAlchemy import for Text and adjusted the query column in the notify_sql table to be a TEXT column instead of a varchar(200000).
Here are the edits:
and the table definition change:
Let me know if I can be of more help.
The text was updated successfully, but these errors were encountered: