Skip to content

SQL: resolve legacy mode + deprecate mysql flavor (GH6900) #7077

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

Merged
merged 1 commit into from
May 11, 2014

Conversation

jorisvandenbossche
Copy link
Member

  • removed warning for not using sqlalchemy (as sqlite DBAPI connection is fully supported, no warning needed)
  • added deprecation warning for 'mysql' flavor
  • removed necessity of providing flavor kwarg (no warning if not provided, assumed to be sqlite3)
  • removed flavor kwarg from execute and read_sql_query (because a) are not database specific functions + b) would only be needed for mysql, but this will is deprecated so no need to introduce it)
  • updated the tests to reflect this
  • updated docs and docstrings to reflect that sqlite3 is the only but fully supported DBAPI connection (no 'legacy')

Closes #6900.

- removed warning for not using sqlalchemy (as sqlite DBAPI connection is fully supported, no warning needed)
- added deprecation warning for 'mysql' flavor
- removed necessity of providing flavor kwarg (no warning if not provided, assumed to be sqlite3)
- removed `flavor` kwarg from execute and read_sql_query (because a) are not database specific functions + b) would only be needed for mysql, but this will is deprecated so no need to introduce it)
- updated the tests to reflect this
- updated docs and docstrings to reflect that sqlite3 is the only but fully supported DBAPI connection (no 'legacy')
@jorisvandenbossche
Copy link
Member Author

@hayd @danielballan @jreback This can use some carefull review I think.

@danielballan
Copy link
Contributor

Looks thorough and correct. I can't find an issue.

@jorisvandenbossche
Copy link
Member Author

OK, then I am going to merge this. Further comments are always welcome after-merge! (but it's a bit difficult to futher work on the sql code with a lot of PRs open)

jorisvandenbossche added a commit that referenced this pull request May 11, 2014
SQL: resolve legacy mode + deprecate mysql flavor (GH6900)
@jorisvandenbossche jorisvandenbossche merged commit cba041e into pandas-dev:master May 11, 2014
@jorisvandenbossche jorisvandenbossche deleted the sql-legacy branch May 11, 2014 09:54
@jorisvandenbossche jorisvandenbossche added the IO SQL to_sql, read_sql, read_sql_query label Jul 11, 2016
@jorisvandenbossche jorisvandenbossche added this to the 0.14.0 milestone Jul 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
IO SQL to_sql, read_sql, read_sql_query
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SQL: Status of the legacy mode?
2 participants