Dialect does not autocommit for TRUNCATE Table Statement about sqlalchemy-exasol HOT 6 CLOSED

@hoffmann not an upstream change. I assume the regex can be overwritten in the EXASOL specific dialect. If this is not possible the method needs to be overwritten.

from sqlalchemy-exasol.

quickly looking at it, the fix should redefine the referred regexp
https://github.com/zzzeek/sqlalchemy/blob/b9d0e2d5c55f68193fae001bb553a51018ab8ed6/lib/sqlalchemy/engine/default.py#L26

From what I see, MERGE and TRUNCATE should be added to the list.

from sqlalchemy-exasol.

Maybe you should ask the other way round:
Is there any statement on Exasol that should/can not be autocommitted?

from sqlalchemy-exasol.

@BY-jk I'm not sure If upstream is willing to include statements in sqlachemy that are specific to certain dialects and not supported by all.

from sqlalchemy-exasol.

@exaSR I don't want to change the standard commit behaviour for eg SELECT statements, because a commit might trigger INDEX builds/updates. So I'd like to have a list of all data changing statements.

from sqlalchemy-exasol.

@hoffmann Actually, the SELECT might trigger an index build, while the commit would publish that index such that it does not get built repeatedly by other transactions...
In Exasol, basically any statement could be data-changing when you classify table statistics and indices as data.

But I agree, never change a running system unless there are problems.

from sqlalchemy-exasol.