Enable supports_statement_cache for Db2 SQLAlchemy dialects #188
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses issue #187 and enables SQLAlchemy statement cache support for the Db2 SQLAlchemy dialect (
ibm_db_sa).The change refactors LIMIT / OFFSET SQL compilation to ensure that:
ROW_NUMBER()while remaining cache-friendlyAs a result, the dialect can safely advertise:
For more info related to it, please go through below documentation links of SQLAlchemy
Dialect caching support: https://docs.sqlalchemy.org/en/20/core/internals.html#sqlalchemy.engine.Dialect.supports_statement_cache
Caching requirements for third-party dialects: https://docs.sqlalchemy.org/en/20/core/connections.html#engine-thirdparty-caching