Ensuring that select * with aggregate is controlled with users hitting the requests so the database does not slow down. (This does not include pagination, which can solve this issue) #261
Unanswered
rkumar0322
asked this question in
Q&A
Replies: 1 comment
-
When you issue named queries in development mode they are saved to an allow-list. In production mode only queries from this allow-list are a compiled into prepared statements are available to be used. There is no dynamic compiling of queries in production mode hence the client cannot change the query. In short this is a non-issue users cannot change the query. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Is there a way that developers can limit users from executing GQL queries where the SQL query will slow down the database such as
select * from table order by column where column = x
?Beta Was this translation helpful? Give feedback.
All reactions