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
Hello,
I tested after upgrading from version 2.3.3 to 3.0.0 of Pinpoint.
Although the API logic is successfully executed and the API status code is 200, why is it detected as an Exception in PINPOINT? After running several tests, it seems to occur when there are a large number of insert or update queries. Are there any specific settings I need to adjust?
Additionally , There were no issues when calling the same API in version 2.3.3.
�Thanks
The text was updated successfully, but these errors were encountered:
Starting from version 3.0.0, to enhance visibility of potential n+1 queries, if more than 100 queries are executed within a single transaction, it will be marked as an error.
You can disable this feature by adding the option -Dprofiler.sql.error.enable=false, and you can adjust the threshold with the -Dprofiler.sql.error.count option.
Hello,
I tested after upgrading from version 2.3.3 to 3.0.0 of Pinpoint.
Although the API logic is successfully executed and the API status code is 200, why is it detected as an Exception in PINPOINT? After running several tests, it seems to occur when there are a large number of insert or update queries. Are there any specific settings I need to adjust?
Additionally , There were no issues when calling the same API in version 2.3.3.
�Thanks
The text was updated successfully, but these errors were encountered: