9
96%
master: 92%

Ran 25 Jan 2017 11:42PM UTC

Files 73

Run time 3s

Badge

Embed ▾

Committed 25 Jan 2017 11:28PM UTC coverage: 84.997% (+0.07%) from 84.923%

Job # ENV=pymysql

Build Type

push

travis-ci

Committed by

jamadden

Commit Message

Better DBAPI compliance: don't depend on cursor.rowcount and full resultset buffering

This is a good thing in general.

In MySQL Connectors case, it means we can get away from using the
`buffered=True` parameter when we get a cursor, which is a necessary
step to being able to use prepared cursors (because the two types can't
be combined).

It also *massively* improves performance. Using a buffered cursor,
running the testmysql tests took 173s with the python driver; using the
default unbuffered cursor they go to ~129s, which is comprable to
PyMySQL's ~125s. The C implemenattion goes to 115s (I didn't get a
before number for it) which is comprable to mysqlclient's 111s.

It makes me wonder what using unbuffered queries in those two
implementations might look like. mysqlclient appears to use one API call
to buffer the entire result set (mysql_store_result). PyMySQL seems to
iterate "packet" by packet, while connector/python iterates "row" by
row, which appear to be the same. This requires further testing.

Run Details

4623 of 5439 relevant lines covered (85.0%)

0.85 hits per line

zodb / relstorage / 583 / 9
96%
master: 92%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 583.9 (ENV=pymysql)

zodb / relstorage / 583 / 9 96% master: 92%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 583.9 (ENV=pymysql)

zodb / relstorage / 583 / 9
96%
master: 92%

README BADGES
x