Michael König

Hi! Thanks for the report. Could you try to cast the JSON field to VARCHAR as a workaround?

Makes perfect sense, Dave.

Hi! Exposing some metadata should not be too much of a problem. As a workaround, you could attach metadata yourself, doing something like ``` my_arguments = {...} connection = turbodbc.connect(**my_arguments)...

@karthik17 The `parameter_sets_to_buffer` option directly determines the batch size of the parameter transfer. The larger the value is, the less database roundtrips occur. This often leads to better performance until...

To work around you problem, you could query the `SmallDateTimeColumn` by using a `CAST()` to the `date` time. I suppose that the database knows how to make this cast efficiently,...

You can compare the type code to turbodbc's type codes `STRING`, `NUMBER`, and `DATETIME`: https://github.com/blue-yonder/turbodbc/blob/master/python/turbodbc/data_types.py#L20 This practice is suggested by PEP-249. I am not sure what you are trying to...

This is one of the problems currently seen in the windows_ci branch, since AppVeyor already ships a MySQL 5.7 database. The issue does not appear with MySQL 5.6 (as on...

Update: According to [MySQL bug #67702](https://bugs.mysql.com/bug.php?id=67702), you can work around by setting the connection option `no_ssps = "1"`. This will disable server-side prepared statements in favor of emulating prepared statements...

Hm, perhaps this has something to do with missing autocommits? The operations seem to involve the Data Definition Language part of SQL, and some databases require commits after such operations...

``` >>> cur.execute("CREATE TABLE test (a integer)") >>> cur.execute("INSERT INTO test VALUES (?)", [42]) >>> cur.execute("CREATE TABLE #test (a integer)") >>> cur.execute("INSERT INTO #test VALUES (?)", [42]) Traceback (most recent...