-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FOGL-2124 enable Foreign key constraint in SQLite #339
base: develop
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Also I have noticed that whenever we attempt an invalid logcode in POST audit request. Only Sqlite engine query retries upto 40 times. Is this valid? See the below syslogs:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No we have any indication of a performance impact?
I think SQLExec should handle error like SQLITE_CONSTRAINT, log and exit the loop instead of assuming BUSY/LOCKED & retrying with hard coded MAX_RETRIES 40 if rc != SQLITE_OK. |
@MarkRiddoch Check below if makes any sense
Result
-ve scenario
+ve scenario
-ve scenario
+ve scenario
|
JIRA https://scaledb.atlassian.net/browse/FOGL-5197 raised so that we do not forgot to fix this issue. (Suppress warnings) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can not merge this with the retry issued raised by @ashish-jabble - please hold until this is resolved.
as expected fledge_nightly_build_ub1804/614/testReport/junit/api.test_audit/ test_create_audit_entry with nonexistent (reference) log code fails now.
Bad entry tests updated in https://github.com/fledge-iot/fledge/pull/322/files