relation loads records after 20 Minutes unexpectedly

Classic Servoy
1

My foundset loads Records after 30 Minutes idle-time, but unexpected. I have no process running, no user action, just nothing.
It loads records who are outside of my find() search() range.

The Solution http://212.112.253.21:8080/servoy-webclient/ss/s/GigDoodle/m/myDeepLink/a/mao8mt81pdcouppj6a0q6bbis6
loads a bunch of records, using a relation with a variable on the left side, like:

globals.gFiltBand_id = globals.gJSRecUSER_USER[‘band_id’]
if (band_filt.getSize() != 1){
return false
}

After this I use find/search:

term_filt.sort(‘vonjjmm asc, sortnr asc’)
term_filt.find()
term_filt[‘vonjjmm’] = cVonJJMM + ‘…’ + cBisJJMM
term_filt.search()

Then I show the data as a kind of calendar. If the user dosn’t change anything, the
foundset “term_filt” loads Records outside of my range.

I know this, because the records are not at the same position ( term_filt.getSelectedIndex() ) after 30 minutes.

Any Ideas welcome, thanks.

2

Is this a known feature, that a relation loads additional records (outside of the range of find/search)
from database after 30 minutes idle time ?

Thanky you for any suggestion.

3

no there should suddenly not be a load that is happening out of the blue

If you really have 20 minutes doing nothing then caches could be cleared out, so if you touch something again relations could be reloaded.

4

…relations could be reloaded.
Yes, this is possible, but the reload ignores the given find/search filter !

i try to create a little test.servoy to reproduce it, and then file a case

thank you

5

to be clear, you have a related foundset, where you set search criteria on (besides the related criteria)
and then you don’t use the relation at all for a while (its not hold on to in the ui or anything)
and then you do record.relation or something and then the find criteria is gone?

That’s something that can happen yes. Because we can’t keep all foundset (that has the query state in it) live in memory all the time
So they will be flushed, and because of that you will loose for that related instance the find criteria

I think you can really assign the related foundset instance to a global variable (or global array)
so that it never gets removed from memory

6

If it can happen that I loose the filter criteria, but still have my foundset,
it means it can happen that my foundset suddenly has different data at a
unknown moment, without any programactions.

A hint in the documentation would be nice.

Thank you Johann.