-
Notifications
You must be signed in to change notification settings - Fork 236
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
Remember token column not recognized #30
Comments
Can you make PR please? It would be nice to have you as a contributor! :) |
VeeeneX
added a commit
that referenced
this issue
Feb 20, 2017
Merged
VeeeneX
added a commit
that referenced
this issue
Feb 20, 2017
* Updates - Added testing Model - Fix for #18 - Fixed issues with 'CURRENT_TIMESTAMP', 'NULL ON UPDATE CURRENT_TIMESTAMP', 'CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP' - Check for non existing column types - Fixed index keys, primary key is no longer included - Added .gitignore * Updates - Added testing Model - Fix for #18 - Fixed issues with 'CURRENT_TIMESTAMP', 'NULL ON UPDATE CURRENT_TIMESTAMP', 'CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP' - Check for non existing column types - Fixed index keys, primary key is no longer included - Added .gitignore * Fix for #30 And possible for padding as well as small fixes
@mitto98 Merged closing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've found a bug at row 301, i've fixed it in a local version
if col.name == 'remember_token' and typesDict[col_type] == 'string' and str(col.length) == 100:
if col.name == 'remember_token' and typesDict[col_type] == 'string' and str(col.length) == '100':
The text was updated successfully, but these errors were encountered: