| Optimization batch reading collection after invalidation [message #1809365] |
Sun, 14 July 2019 22:53  |
Eclipse User |
|
|
|
Any optimization available in EclipseLink that would avoid doing a SQL for each item in the collection having expired children?
You can run the main entry from the class Application, the log will finish with the output below, showing one select for each item in the collection. I'm looking for an existing feature in EclipseLink that could make this not happening. I believe Hibernate can handle that with https://docs.jboss.org/hibernate/orm/3.5/reference/en/html/performance.html#performance-fetching-batch.
If no feature exist to handle that, could you open a feature request?
[EL Fine]: sql: 2019-07-10 18:01:37.248--ServerSession(1837601499)--Connection(17331878)--Thread(Thread[main,5,main])--SELECT ID, FIRSTNAME, LASTNAME FROM ADDRESS WHERE (ID = ?)
bind => [2]
[EL Fine]: sql: 2019-07-10 18:01:37.249--ServerSession(1837601499)--Connection(1311052922)--Thread(Thread[main,5,main])--SELECT ID, FIRSTNAME, LASTNAME FROM ADDRESS WHERE (ID = ?)
bind => [3]
[EL Fine]: sql: 2019-07-10 18:01:37.25--ServerSession(1837601499)--Connection(810576909)--Thread(Thread[main,5,main])--SELECT ID, FIRSTNAME, LASTNAME FROM ADDRESS WHERE (ID = ?)
bind => [4]
[EL Fine]: sql: 2019-07-10 18:01:37.25--ServerSession(1837601499)--Connection(1629759610)--Thread(Thread[main,5,main])--SELECT ID, FIRSTNAME, LASTNAME FROM ADDRESS WHERE (ID = ?)
bind => [5]
[EL Fine]: sql: 2019-07-10 18:01:37.251--ServerSession(1837601499)--Connection(775423528)--Thread(Thread[main,5,main])--SELECT ID, FIRSTNAME, LASTNAME FROM ADDRESS WHERE (ID = ?)
bind => [6]
Attachment: Sample.zip
(Size: 10.67KB, Downloaded 163 times)
|
|
|
|
Powered by
FUDForum. Page generated in 0.02948 seconds
Home