-
Notifications
You must be signed in to change notification settings - Fork 17
Commits to increase test coverage #8
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
Conversation
…amed because they match the table name
… true, TRUNCATE statements were not getting written out. increase test coverage to 91%
My newest pull request includes these commits as well. Note all tests do run successfully. |
tardate, would it be better if I submitted this to maxlapshin's branch? I'm not sure where the best place is for these changes. |
maxlapshin has been rather unresponsive on a few month's worth of pull requests on his repo--it might be beneficial for someone to ask him if he would like someone else to take over managing the primary repo. |
…ames because they might not be unique or might collide with table names
Commits to increase test coverage
mysql2postgres is awesome. I spent some time increasing test coverage to encourage further development and prevent regressions.
I added tests for:
Thank you!
Aaron