Why we need @Transaction Attribute in spring for only select statement - NO ddl in service layer

Asked Mar 19 '21 at 15:20

Active Mar 19 '21 at 17:59

Viewed 734 times

I read multiple threads but I didn't get the answer to why we need to use @Transaction attribute for the select query.

Assume we don't have any other DDL statements just plain select statements which read data and displays on UI.

Transaction attribute provides isolation, so If I don't use @Transaction attribute it may possible it will show me the most recent data which will be good, isn't it?

Could you please provide me any reference article link , share your knowledge, pros and cons for only @Transaction use with Select statements.

edited Mar 19 '21 at 17:59

James Z

12,209
10
24
44

asked Mar 19 '21 at 15:20

Jordan

Which Database are you using? Are you using JPA? – Simon Martinelli Mar 19 '21 at 15:27
We are using spring jdbc and we are putting the @transaction at method level not the class level. – Jordan Mar 19 '21 at 17:33
This might be a good read for you. https://stackoverflow.com/questions/13539213/why-do-i-need-transaction-in-hibernate-for-read-only-operations – aksappy Mar 19 '21 at 18:05
And what database? – Simon Martinelli Mar 19 '21 at 18:24
We are using oracle as database – Jordan Mar 19 '21 at 18:41

Why we need @Transaction Attribute in spring for only select statement - NO ddl in service layer

0 Answers0