-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Un-Graceful exit when table with 'real' datatype is created #65
Comments
Not sure if this was the right way to fix it, but made the following changes to ColumnDef.java and FloatColumnDef.java. ColumnDef.java: case "float":
case "real":
case "double":
return new FloatColumnDef(tableName, name, type, pos); FloatColumnDef.java public boolean matchesMysqlType(int type) {
if ( getType().equals("float") || getType().equals("real"))
return type == MySQLConstants.TYPE_FLOAT;
else
return type == MySQLConstants.TYPE_DOUBLE;
} It seems to solve the problem and Maxwell accepts it without a hitch. Not sure about best practices though. Please take a look and see if this is a suitable solution. |
looks fine, can you do this as a PR (with a test) & I'll merge it? |
I have no idea of how to do that. Sorry :( |
#68 fixes this. Thanks! |
Similar to #64, Maxwell chokes when it encounters a field with
real
type.Maxwell error with real datatype:
After error with real, subsequent runs fail:
The text was updated successfully, but these errors were encountered: