Strage behaviour with Clickhouse 20.1 using Superset about clickhouse-sqlalchemy HOT 3 CLOSED

The same issue: #14

There is a FORMAT trick for HTTP transport that requires custom session.

from clickhouse-sqlalchemy.

Thanks for the quick response - that's spot on! One follow up question: As we do not have access to the code directly as we're using sqlalchemy underneath Superset - is there a way to change behaviour based on connection parameters - enforcing "FORMAT TabSeparatedWithNamesAndTypes" ? Or are we doomed in this case?

Also it would be great to add some more details to the readme (which I was indeed reading), but it's not very obvious there's different behaviour by engine call vs session call (nor is it intuitive). When starting with a green field project, you'll directly hit this, so no problem, but if it's covered behind a tool it's a really no big fun debugging.

from clickhouse-sqlalchemy.

Sorry for late response. You can specify different DSN: clickhouse+native:// as database endpoint. Native protocol does not require explicit FORMAT clause rendering.

from clickhouse-sqlalchemy.