-
-
Notifications
You must be signed in to change notification settings - Fork 851
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
Update enforce statement for parent id database query (Issue #912) #913
Conversation
abraunegg
commented
May 8, 2020
- Remove redundant enforce check as if the parent is not in the database, the previous statement ensures the parent is in the database. If the parent is a shared folder, the parent ID will never be in the database as we are never provided it.
* Remove redundant enforce check as if the parent is not in the database, the previous statement ensures the parent is in the database. If the parent is a shared folder, the parent ID will never be in the database as we are never provided it.
Seems fine to me and understandably, but why was it there in the beginning, and could it have consequences for other usage patterns/combinations so that different failures occur? I.e., if it is not a shared folder, can it still be not in the database? |
@norbusan
The same query is being used above, to check if the parent path is in the database, and if not, then add it. Now - could leave the enforce in, but do this:
This has the same net effect. |
Indeed indeed, that is what I meant. Thanks. |
* Update fix to leave enforce in place, but with conditional check on parent drive id.
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |