Skip to content

DOC: Document existing functionality of pandas.DataFrame.to_sql() #11886 #26795

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 20 commits into from
Aug 30, 2019
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Now passes flake8
  • Loading branch information
oguzhanogreden committed Jun 11, 2019
commit 4397fc7376ec5fda3cda5b038c836a6f1c7bbf48
8 changes: 4 additions & 4 deletions pandas/core/generic.py
Original file line number Diff line number Diff line change
Expand Up @@ -2494,10 +2494,10 @@ def to_sql(self, name, con, schema=None, if_exists='fail', index=True,
Rows will be written in batches of this size at a time. By default,
all rows will be written at once.
dtype : dict or a SQLAchemy type, optional
Specifying the datatype for column(s). If a dictionary is used, the keys
should be the column names and the values should be the SQLAlchemy types
or strings for the sqlite3 legacy mode. If all columns are of the same
type, one single value can be used.
Specifying the datatype for columns. If a dictionary is used, the
keys should be the column names and the values should be the
SQLAlchemy types or strings for the sqlite3 legacy mode. If all
columns are of the same type, one single value can be used.
method : {None, 'multi', callable}, default None
Controls the SQL insertion clause used:

Expand Down