You are not logged in.
Pages: 1
We already have a DB query result size limitation, but I found this is not enough for stable REST API.
There is a situations when a small amount of data returns too long (full scan on huge table because of like '%bla-bla%' etc.)
To prevent such a situations for a REST instances I limit a statement execution time on the DB level.
For Oracle I uses a resources groups, for Postgres - a 'statement_timeout' session variable.
For SQL Server the only applicable solution I found is SQL_QUERY_TIMEOUT
and implement such timeout by PR #395
@ab, I will port it to mORMot2 when will be approved for mORMot1
Last edited by mpv (2021-05-01 10:24:04)
Offline
Thanks. Back-ported to mORMot2 - https://github.com/synopse/mORMot2/pull/29 (not tested since there is no tests for mORMot2 ODBC yet) but hope will work
Offline
Pages: 1