Group Design for Data Cache

Hello,

As Nathan mentioned, Ignition has corrected one big flaw in how FactorySQL performed data caching, which was that it was reactionary, only storing data to the cache once the connection was determined to be down. This could lead to a delay in the data, because it can sometimes take a fair amount of time to determine this. With some group types in FactorySQL, “buffered execution” was introduced, in order to minimize this effect. Stored Procedure groups do not support this.

Furthermore, stored procedure groups in Ignition don’t currently pass through the store and forward system. So, in both products, your best bet is to adapt your project to write directly to the database with History or Standard groups.

Using this historical group, which used buffered writing, you shouldn’t see any gap in the data.

Also, the main requirement for groups to use datacaching is that they can’t require anything from the database during execution- so, they can’t have action items that run queries.

Regards,