Le dimanche 01 septembre 2013 21:15:09 Apatira Lookman a écrit : > use stateless session with batch insert
I have no problem on insert, only on select. Solution rejected because just a tricky workaround which break all the other part of any app… My problem is not *how* I can solve my problem (seems FlushMode.NEVER solve it) but *why* I have the problem, because the observed behaviour is totally tricky : - session is empty because newly created at the « SELECT FROM System » time - this query take few ms on direct SQL - this query return at most only 1 result - this query return only 1 row and have no association or other thing which can lead to some data fetching Worst, inserting totally not related datas in another totally not related session leads to timing problem. So I have no clue to what causes this timing problem. Is it not scary to you to not understand the root cause and just scatter to the four winds some random « fix » which can lead to worst problem than the fixed one ? A good engineer not only fix a problem with random code copy/pasted from the web, but must also determine the cause of the problem. Because on next projets, I want to be able to know what problem I can meet and why I can focus on such technology or other. -- Nicolas Vinot
signature.asc
Description: This is a digitally signed message part.
