FAIL: test.test_suite.DateTimeMicrosecondsTest.test_round_trip about sqlalchemy-exasol HOT 3 CLOSED

Confirming this on (python 2.7.5, sqlalchemy 0.8.2, exaODBC 4.1.2, EXASolution 4.2.7)

EXASolution only supports timestamps with millisecond fractions, not microseconds.
Changing the tested timestamp from (2012, 10, 15, 12, 57, 18, 396) to (2012, 10, 15, 12, 57, 18, 396000) lets us pass the test, which of course no longer checks for microseconds.

Possible solutions:

1. Turn off microsecond support in the dialect. We will also lose milliseconds.
2. Enhance sqlalchemy and the test framework to differentiate between milli-, micro- and nanosecond precision.
3. Ignore/disable the testcase for this dialect.
4. Ask Exasol to add microsecond precision for timestamps.

from sqlalchemy-exasol.

My preferred order of solving this is:

2 - enhance SQLA test framework. This is where this should be handled. A pull request for SQLA for versions 0.8.x and 0.9.x is required.

in parallel:
1 - but only as a temporary workaround because it would be a pity to loose this precision
4 - at least post the request

last option:
3

from sqlalchemy-exasol.

To get to a green build I have disabled the test for microseconds with commit e0b530b.
I will add a new issue to send a pull request to upstream project SQLA for test suite enhancement.

from sqlalchemy-exasol.