[Feature]: Need a connection pool for querying H2

[sumitsum]

Is there an existing issue for this?

• I have searched the existing issues

Summary

• Currently, we used H2 in memory database as a temporary data store and we perform our where, pagination, sort, and projection queries on top of it. The plugin opens a new connection with every action invocation. This can saturate the permissible connection limits very soon. Hence, it may be useful to use a connection pool instead.

Why should this be worked on?

To avoid failure of features like where, sort etc that are provided as part of UQI experience.

[rohan-arthur]

@sumitsum I don't understand this - are you referring to how we process the action components in our backend? It might help me to understand better if you can frame this as how the user sees the problem.