Skip to content
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

Added Engine Disposal Documentation #27972

Conversation

poojahagawane
Copy link

Created hyperlink to SQLAlchemy docs for Engine Disposal
responsibilities of user. Unified wording of legacy support for sqlite

@gfyoung gfyoung added Docs IO SQL to_sql, read_sql, read_sql_query labels Aug 18, 2019
or DBAPI2 connection (fallback mode)
Using SQLAlchemy makes it possible to use any DB supported by that
library. Legacy support is provided for sqlite3.Connection objects.
Note: The user is responsible for engine disposal and connection
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Note: The user is responsible for engine disposal and connection
Note: The user is responsible for engine disposal and connection

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For these "Note:" sections, let's add a newline above (this applies to your other changes)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey I added the newline however its not rendering in the documentation generated.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think they end up in the same paragraph in the generated HTML.

emattiza and others added 2 commits August 18, 2019 12:10
Created hyperlink to SQLAlchemy docs for Engine Disposal
responsibilities of user. Unified wording of legacy support for sqlite
@WillAyd
Copy link
Member

WillAyd commented Aug 27, 2019

Can you fix merge conflict and address comments?

@@ -72,7 +72,6 @@ I/O

- Avoid calling ``S3File.s3`` when reading parquet, as this was removed in s3fs version 0.3.0 (:issue:`27756`)
- Better error message when a negative header is passed in :func:`pandas.read_csv` (:issue:`27779`)
- Follow the ``min_rows`` display option (introduced in v0.25.0) correctly in the HTML repr in the notebook (:issue:`27991`).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you revert this file

@jreback
Copy link
Contributor

jreback commented Oct 6, 2019

can you merge master and revert the 0.25.1 file

@WillAyd
Copy link
Member

WillAyd commented Oct 22, 2019

Nice idea but looks like this has gone stale so closing; ping if you'd like to pick this back up

@WillAyd WillAyd closed this Oct 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Docs IO SQL to_sql, read_sql, read_sql_query
Projects
None yet
Development

Successfully merging this pull request may close these issues.

It is not clear whether database connection need to be closed manually after calling pd.read_sql()
6 participants