Commented out default driver name for turbodbc

[pmetzner]

The default driver name kept sabotaging queries, so I hotfixed it by commenting it out.

[jank]

@MathMagique can you have a look at this PR? Also have a look at PR #59 where the default driver name was wrong for Windows (and fixed) as I am not sure if this is related.

[MathMagique]

@BY-jk Yes, it seems that would be related. It is not a turbodbc-specific issue (PR #59 is about pyodbc). The issue is that sqlalchemy_exasol assumes a default driver name that is neither universal nor necessary. Changing the default as in #59 will break code for everybody that relied (implicitly) on the previous default.

@pmetzner's pull request shifts the responsibility to set the driver to the user, and that is the only person who can really know what the driver's name is. Also, using the data source name in the connection options usually implies that the driver is already configured correctly, so there is no need to mention it again. That seems to be what Paul ran into.

My advice would be to extend this pull request to the pyodbc part as well, and to remove all traces that there ever was a default. The documentation would then need to be extended with a note saying that one needs to specify the driver manually, and how to find out the driver's name. This would be the honest option and should avoid further pull requests of users tring to change the default to what suits their system.

[jank]

Closed in favor of: #66