Catch the exception type the claim conflict actually throws

Ya: 7 Agosti 2026, 07:19 UTC
Mwandishi: Kamo
Ahadi ya: f64b5c2

Round 2 review fix: the statement-level 40001 (the common case, detected inside executeUpdate() rather than at commit) surfaces as **************** via Hibernate's ExceptionConverterImpl, not as a Spring ConcurrencyFailureException. SupportTicketService is @Service, not @Repository, so nothing translates it on the way out. The controller now catches both types; the commit-time ConcurrencyFailureException path (the rarer case) still works as before. Split the round-1 serialization test in two so both surfacing paths are pinned instead of one Spring-only type standing in for both.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru Milele Mtazamo wa bei