Aside from doing a direct match on something like a whitespace normalized hash of a query, what might be a useful (but-not-necessarily-perfect) way to handle query cache in a partial manner? For example, let’s take the following basic case: This potentially could be used as a ‘base-cache’ upon which a further query could be executed to potentially improve performance: So,
Tag: caching
How to get Ignite Cache SQL Query to Return Value Object
I have a Postgres database configured as my persistence layer and would like to execute SQL queries against the Postgres tables cached in Ignite. Ideally, I’d like to execute a query on these caches and be returned the Value objects represented by these tables. SqlQuery gives me the functionality that I am looking for but is deprecated. SqlFieldsQuery would work,
Improve pivot view performance
I have a key-value structure for storing dynamic entities (standard EAV). I made a view for this Entity with the Pivot command. I tried to set the index for this view, but it is not possible due to the use of pivot. Is there a way to drag my data into SQL at the time of insert, Update? Because performance
Caching SQL queries
If I look in my profiler for SQL-server, it comes up with a lot of duplicate queries such as: A lot of these queries are not needed to display real time data, that is, if someone inserted a new record that was matched in that query it wouldn’t matter if it didn’t display for up to an hour after insertion.