| Re: [jta-dev] Enhancement of the @Transactional Annotation |
Hi,
Marking a transaction as read only has some nice performance benefits as that can allow Hibernate/JPA to avoid some costly operations. Also, I think it would be nice if the datasource implementation could switch between actual connection pools based on the read-only flag, to e.g. direct read-only queries to a hot-standby instead of the primary database.
+1 from me for this!
Hi,
Sounds useful to me indeed. Thanks for starting this.
Kind regards,Arjan Tijms
On Sun, Dec 4, 2022 at 4:44 PM Benedict Eisenkrämer <benedict@xxxxxxxxxxxxxx> wrote:
_______________________________________________Hello there,
I am new to this mailing list so maybe a few short words to myself first: I am a Software Engineer in Germany responsible for our JavaEE, soon to be JakartaEE framework. I am quiet interested in JakartaEE and its development.
The topic I would like to discuss is the enhancement of the @Transactional Annotation for JakartaEE 11. A good template would be the Spring specific Annotation of the same name which supports among other things :
- Isolation levels
- timeout
- readOnly
I already found a issue on github regarding the Topic, which unfortunately has not seen any attention given to it since 2016. So I wanted to spark a discussion.
In my opinion these enhancement could be quiet helpful.
Thanks in advance and best regards
Benedict Eisenkrämer
jta-dev mailing list
jta-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jta-dev
_______________________________________________ jta-dev mailing list jta-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jta-dev