Hello! SQL queries have no isolation currently so it is not possible to avoid the problem that you described. You could try switching to ScanQuery, see if it helps; or learning to deal with duplicates.
Regards, -- Ilya Kasnacheev пт, 23 нояб. 2018 г. в 19:25, Sobolewski, Krzysztof < [email protected]>: > Hi, > > I'm wanting to use a ContinuousQuery and there is a slight issue with how > it transitions from the initial query to the notifications phase. It turns > out that if there are additions to the cache happening while the continuous > query runs, an entry may be reported twice - once by the initial query and > once by the listener. This is confirmed by experiment, BTW :) The initial > query in this case is an SqlQuery. > > So my question is: is this intentional? Or is it a bug? Is there something > I can do to mitigate this? Is this is an issue of isolation level? > > Thanks a lot for any pointers :) > -KS > > ________________________________ > > Your Personal Data: We may collect and process information about you that > may be subject to data protection laws. For more information about how we > use and disclose your personal data, how we protect your information, our > legal basis to use your information, your rights and who you can contact, > please refer to: www.gs.com/privacy-notices< > http://www.gs.com/privacy-notices> >
