Tables…bounce process after modify???

[Tom Rioux]

I was under the impression that whenever you modified or added entries into a table, you had to either bounce the process or purge the caches in order for the change to take affect.   In doing some testing with tables, I modified some tables and ran messages through the interface via NetMonitor.   I made changes to an existing entry in the table but didn’t do a bounce or a purge, and the expected value was translated to the message.  I added an entry into the table but didn’t do a bounce or a purge, and the expected value once again was translated to the message.

Now, I’m on Cloverleaf 5.2, does the “bounce the process” or “purge the cache” thinking still hold true for modifications to tables?

Thanks…

Tom Rioux

Topic

[Jim Kosloskey]

Tom,

We are also on Cloverleaf(R) 5.2 and the last time I made a change to a Table I needed to do a ‘Purge Caches’ to activate it.

If I have time, I will try another test.

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Rob Abbott]

I’m not aware of any change in any release regarding this.  

Note that tables are loaded on demand, not at startup.   Once loaded the table is cached.  If the table is changed, bouncing the process or purging the cache will cause the table to be reloaded next time it’s needed.

Rob Abbott
Cloverleaf Emeritus

[Author]

Replies