You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that when using the executeTakeFirstOrThrow, the resulting error will contain the query node by default if the query fails to find any results. In many cases that might not be a big issue, but for some applications that handle personally identifiable information, this can cause some problems.
Now, one can pass the errorConstructor to the function, but it can be a bit annoying and error-prone to copy-paste it in many places. Thus, I'm wondering if it would make sense to add the possibility to globally configure it somehow, so that the compiled query would not be logged by default? Or at least an option to filter out the nodes that contain the actual values.
The text was updated successfully, but these errors were encountered:
woltsu
changed the title
executeTakeFirstOrThrow includes the compiled query in the error by default
executeTakeFirstOrThrow includes the query node in the error by default
Apr 17, 2024
It's the same underlying nodes, just with some extra metadata.
We could then transform the tree before throwing. Produce a redacted sql string on-demand.. etc.
Hello, and thanks for the amazing library! 馃憢
I noticed that when using the
executeTakeFirstOrThrow
, the resulting error will contain the query node by default if the query fails to find any results. In many cases that might not be a big issue, but for some applications that handle personally identifiable information, this can cause some problems.Now, one can pass the
errorConstructor
to the function, but it can be a bit annoying and error-prone to copy-paste it in many places. Thus, I'm wondering if it would make sense to add the possibility to globally configure it somehow, so that the compiled query would not be logged by default? Or at least an option to filter out the nodes that contain the actual values.The text was updated successfully, but these errors were encountered: