Skip to content

Manage transaction name when use @Transactional annotatnion #848

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
soql opened this issue Dec 13, 2023 · 1 comment
Closed

Manage transaction name when use @Transactional annotatnion #848

soql opened this issue Dec 13, 2023 · 1 comment
Labels
for: external-project For an external project and not something we can fix

Comments

@soql
Copy link

soql commented Dec 13, 2023

We have problem with r2dbc and mssql project after update spring 2.7 to 3.1. Spring set transaction name to class+method but mssql limit transaction name to 32 chars. Is there any way (interceptor or something else) to catch setting transaction name and override it ?

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Dec 13, 2023
@mp911de
Copy link
Member

mp911de commented Dec 13, 2023

There's a bit of discussion at spring-projects/spring-framework#30054.

There's no support to provide a transaction name via @Transactional. However, by configuring a TransactionAnnotationParser you can affect TransactionAttribute that contains the name attribute.

As this is a Spring Framework functionality, I suggest reaching out to the Framework team.

@mp911de mp911de closed this as not planned Won't fix, can't repro, duplicate, stale Dec 13, 2023
@mp911de mp911de added for: external-project For an external project and not something we can fix and removed status: waiting-for-triage An issue we've not yet triaged labels Dec 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for: external-project For an external project and not something we can fix
Projects
None yet
Development

No branches or pull requests

3 participants