Transaction Names should be truncated when too long. about r2dbc-mssql HOT 3 CLOSED

agreed -- that could work as well. The reason i suggested truncating the beginning is that if you have two different methods:

com.company.name.here.SomeServiceClass.theMethod1
com.company.name.here.SomeServiceClass.theMethod2

Then truncating the beginning would give both transactions the same name of com.company.name.here.SomeServic, which would make it impossible to differentiate when looking at logs.

from r2dbc-mssql.

MSSQL truncates transaction's name automatically if it exceed 32 characters, so we can simply show warning instead of throwing exception.

from r2dbc-mssql.

Happy to include a truncation. We might not log this event but rather silently accept the fact that we're truncating the transaction name.

The issue originates from a default behavior where you (do/can) not specify the transaction name. Hence we can just remove the obstacle that causes transactions to fail. A natural consequence of truncating is information loss. If the data beforehand would be correct, then we would not run into that issue.

from r2dbc-mssql.