io.rst needs updating to reflect api sql API methods introduced in 0.13

[ghost]

@mangecoeur noted in #4163 (comment)

http://pandas.pydata.org/pandas-docs/stable/io.html#sql-queries
Also needs updating since it doesn't reflect the updated API 
(that was already introduced in 0.13 I think) which uses read_sql 
and to_sql for consistency with e.g. the CSV api.

[jreback]

cc @mangecoeur, @hayd

[mangecoeur]

already done in the new SQL code ENH #4163, i rewrote quite a lot of the docs to take into account both new api and new capabilities.

[ghost]

#4163 is not a PR, do you mean #5950?

[jreback]

what was changed in 0.13.0 for sql?

[jreback]

@mangecoeur @y-p are we just pushing this (the doc updates) to 0.14? or doing anything minimal for 0.13.1?

[ghost]

I'll do it in time for 0.13.1

[ghost]

d155623 was merged for 0.11.1 and introduced the pd.read_sql, pd.to_sql methods.
io.rst was not updated, and the examples continue to show how to import directly from
the io.sql namespace before use. the only method employed in the examples is read_frame.

pd.to_sql seemes to have not been available from the top level namespace in the last 3 releases,
since io/api.py was only updated to include read_sql. I haven't seen issues on that,
which makes me think it sees little use.

We probably shouldn't go back and expunge it in favor of #5950, but I'm uncertain how we should
handle this now, given that #5950 has discussion on top level naming and such.

I suggest we punt rather then paint ourselves into a corner at this point.

[ghost]

Bumped to 0.14

[ghost]

@hayd pushed a change directly to master f30499b, so now the example uses read_sql

[hayd]

Sorry @y-p, I had not seen this issue. Should I revert this?

Actually write_frame is also still mentioned (rather than to_sql ) :s.

[ghost]

It's fine, I just saw it and updated. I push to master directly too when I don't consider
it interesting enough for a PR, but it might be a bad habit.

The methods aren't going anywhere, it's just the toplevel namespace we'll
need to get sorted. Completing the doc update with to_sql would be good.

[jreback]

@jorisvandenbossche @mangecoeur close this? as I think you guys are already on top of docs and have several issues related

[jorisvandenbossche]

Yes, this will be done as part of #6300.