When converting time or datetime values with microseconds, the
calculation was wrong, e.g. a millisecond value of .123 was converted
to .000123 instead of .123000. This was already fixed in C/C but not
in C/Python.
Fixed crash when fetching GEOMETRY column. Don't handle GEOMETRY
column type as a string value, instead we need to convert it to
a Python binary object.
Since we can't reset internal members of statement handle (MYSQL_STMT *), we
need to close and reinitialize statement handle in case a different statement
will be executed with same cursor.
We now throw an error if a Python object cannot be converted to the corresponding
MariaDB type instead of serializing it.
This means that Python objects that do not have a corresponding MariaDB server
type must be serialized in the application.
Input/Output or Output parameters have to be retrieved by .fetch methods,
the .sp_outparams attribute indicates if the result set contains output
parameters.
- correct tests according to server/maxscale, and multiple python version
- Cpython (3.6.0, 3.8.0) pypy (3.6-7.2.0), miniconda3-4.3.30
- add scroll test
- benchmark added to test suite. See benchmarks/README.md for info
- cursor.scroll now permit position 0 when using absolute mode
- return Cursor.rownumber None if no result-set, not 0
- exception missing type sqlstate and according tests
While the default paramstyle is still 'qmark', MariaDB Connector/Python
now also supports the paramstyles 'format' and 'pyformat'. The paramstyles
can't be mixed.
* adding file encoding
* test file renamed with test_ prefix permitting unittest discovery
* test configuration using dict using environment data for futur CI testing
* test correction (using table t1) permitting unittest parallel testing
now tests can be run using `python -m unittest -v`
or for python 2 `python -m unittest discover -v`
