GH4163, GH5950, GH6292). All databases supported by SQLAlchemy can be used, such as PostgreSQL, MySQL, Oracle, Microsoft SQL server (see documentation of SQLAlchemy on included dialects). The functionality functionality of providing DBAPI connection objects will only be supported for sqlite3 in the future. The ’mysql’ flavor is deprecated. The new functions read_sql_query() and read_sql_table() are introduced. The read_frame, frame_query, write_frame. Warning: The support for the ‘mysql’ flavor when using DBAPI connection objects has been deprecated. MySQL will be further supported with SQLAlchemy engines (GH6900). 1

GH4163, GH5950, GH6292). All databases supported by SQLAlchemy can be used, such as PostgreSQL, MySQL, Oracle, Microsoft SQL server (see documentation of SQLAlchemy on included dialects). The functionality functionality of providing DBAPI connection objects will only be supported for sqlite3 in the future. The ’mysql’ flavor is deprecated. The new functions read_sql_query() and read_sql_table() are introduced. The read_frame, frame_query, write_frame. Warning: The support for the ‘mysql’ flavor when using DBAPI connection objects has been deprecated. MySQL will be further supported with SQLAlchemy engines (GH6900). 1

GH4163, GH5950, GH6292). All databases supported by SQLAlchemy can be used, such as PostgreSQL, MySQL, Oracle, Microsoft SQL server (see documentation of SQLAlchemy on included dialects). The functionality functionality of providing DBAPI connection objects will only be supported for sqlite3 in the future. The ’mysql’ flavor is deprecated. The new functions read_sql_query() and read_sql_table() are introduced. The read_frame, frame_query, write_frame. Warning: The support for the ‘mysql’ flavor when using DBAPI connection objects has been deprecated. MySQL will be further supported with SQLAlchemy engines (GH6900). 1

now explicitly forbidden. (GH9057) • Bug to handle masking empty DataFrame (GH10126). • Bug where MySQL interface could not handle numeric table/column names (GH10255) • Bug in read_csv with a date_parser GH4163, GH5950, GH6292). All databases supported by SQLAlchemy can be used, such as PostgreSQL, MySQL, Oracle, Microsoft SQL server (see documentation of SQLAlchemy on included dialects). The functionality functionality of providing DBAPI connection objects will only be supported for sqlite3 in the future. The ’mysql’ flavor is deprecated. The new functions read_sql_query() and read_sql_table() are introduced. The

PostgreSQL engine for sqlalchemy pyarrow 0.9.0 Parquet and feather reading / writing pymysql 0.7.11 MySQL engine for sqlalchemy pyreadstat SPSS files (.sav) reading pytables 3.4.2 HDF5 reading / writing or not the joined columns find a match. As of writing, FULL JOINs are not supported in all RDBMS (MySQL). -- show all records from both tables SELECT * FROM df1 FULL OUTER JOIN df2 ON df1.key = df2.key; Angeles 5 Pandas equivalents for some SQL analytic and aggregate functions Top N rows with offset -- MySQL SELECT * FROM tips ORDER BY tip DESC LIMIT 10 OFFSET 5; In [34]: tips.nlargest(10 + 5, columns='tip')

dropped the levels attribute in favor of categories (GH8376) • DataFrame.to_sql() has dropped the mysql option for the flavor parameter (GH13611) • Panel.shift() has dropped the lags parameter in favor now explicitly forbidden. (GH9057) • Bug to handle masking empty DataFrame (GH10126). • Bug where MySQL interface could not handle numeric table/column names (GH10255) • Bug in read_csv with a date_parser GH4163, GH5950, GH6292). All databases supported by SQLAlchemy can be used, such as PostgreSQL, MySQL, Oracle, Microsoft SQL server (see documentation of SQLAlchemy on included dialects). The functionality

dropped the levels attribute in favor of categories (GH8376) • DataFrame.to_sql() has dropped the mysql option for the flavor parameter (GH13611) • Panel.shift() has dropped the lags parameter in favor now explicitly forbidden. (GH9057) • Bug to handle masking empty DataFrame (GH10126). • Bug where MySQL interface could not handle numeric table/column names (GH10255) • Bug in read_csv with a date_parser GH4163, GH5950, GH6292). All databases supported by SQLAlchemy can be used, such as PostgreSQL, MySQL, Oracle, Microsoft SQL server (see documentation of SQLAlchemy on included dialects). The functionality

dropped the levels attribute in favor of categories (GH8376) • DataFrame.to_sql() has dropped the mysql option for the flavor parameter (GH13611) • Panel.shift() has dropped the lags parameter in favor now explicitly forbidden. (GH9057) • Bug to handle masking empty DataFrame (GH10126). • Bug where MySQL interface could not handle numeric table/column names (GH10255) • Bug in read_csv with a date_parser GH4163, GH5950, GH6292). All databases supported by SQLAlchemy can be used, such as PostgreSQL, MySQL, Oracle, Microsoft SQL server (see documentation of SQLAlchemy on included dialects). The functionality

dropped the levels attribute in favor of categories (GH8376) • DataFrame.to_sql() has dropped the mysql option for the flavor parameter (GH13611) • Panel.shift() has dropped the lags parameter in favor now explicitly forbidden. (GH9057) • Bug to handle masking empty DataFrame (GH10126). • Bug where MySQL interface could not handle numeric table/column names (GH10255) • Bug in read_csv with a date_parser GH4163, GH5950, GH6292). All databases supported by SQLAlchemy can be used, such as PostgreSQL, MySQL, Oracle, Microsoft SQL server (see documentation of SQLAlchemy on included dialects). The functionality

dropped the levels attribute in favor of categories (GH8376) • DataFrame.to_sql() has dropped the mysql option for the flavor parameter (GH13611) • Panel.shift() has dropped the lags parameter in favor now explicitly forbidden. (GH9057) • Bug to handle masking empty DataFrame (GH10126). • Bug where MySQL interface could not handle numeric table/column names (GH10255) • Bug in read_csv with a date_parser GH4163, GH5950, GH6292). All databases supported by SQLAlchemy can be used, such as PostgreSQL, MySQL, Oracle, Microsoft SQL server (see documentation of SQLAlchemy on included dialects). The functionality