[HOTFIX][BE] Fix API and DBMS error references #173
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Dicky Herlambang (花） <herlambangdicky5@gmail.com>
Error Info : Missing foreign key (processId) with relation notifyLogs → appLogs, that causing issue failed to transact DB on notificationhelper module run Payload : Foreign key violation: 7 ERROR: insert or update on table "notifyLogs" violates foreign key constraint "notifylogs_processid_foreign" Environment : Production Root cause : foreign key relation are not exist between notifylogs → applogs when insert transact happens Resolution : check and validate if processid between notifylogs → applogs is exists or not, if exists then do nothing. But if not exists then insert it before insert into notifylogs Related Changes : - app\Helpers\NotificationHelper.php Signed-off-by: Dicky Herlambang (花） <herlambangdicky5@gmail.com>
Error Info : On endpoint api/v1/logs/proc/all when using parameter logOrder → asc and logType → access, it throwback error message column \"procStartAt\" does not exist due undefined column in that table. And it causing BE services returning 500 instead of 200 Payload : SQLSTATE[42703]: Undefined column: 7 ERROR: column \"procStartAt\" does not exist\nLINE 1: select *from \"accessLogs\" order by \"procStartAt\" desc limit...\n ^ (Connection: pgsql, SQL: select* from \"accessLogs\" order by \"procStartAt\" desc limit 1000)" Environment : Production Step to reproduce : - access endpoint api/v1/logs/proc/all - use this parameter: * logCount → 1000 * logResult → true * logType → access * logOrder → asc Root cause : Column “procStartAt” are not exist on accessLog table Resolution : Drop filter order by “procStartAt” on getAllLogs function only for access table Related Changes : app\Http\Controllers\Api\Data\notifyLogController.php Signed-off-by: Dicky Herlambang (花） <herlambangdicky5@gmail.com>
Nicklas373
added
bug
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Recent changelog:
composer: Update dependencies
BE-012: Fix null violation DB transact issue
BE-013: Fix undefined column error on logs api