- Issue created by @chucksimply
- 🇮🇹Italy apaderno Brescia, 🇮🇹
To make clearer what the issue is: Before, the code creating a query object was not required to call
accessCheck()
; the query object behaved as ifaccessCheck(FALSE)
was called. Now, the code that creates a query object must callaccessCheck()
for that object, even without arguments, in which case it is equivalent to callingaccessCheck(FALSE)
. - Status changed to Needs review
about 1 year ago 4:30am 13 November 2023 - 🇺🇸United States chucksimply
Thanks @apaderno... patch attached, works for me on 10.1.
- Status changed to RTBC
about 1 year ago 11:58am 13 November 2023 - 🇮🇹Italy apaderno Brescia, 🇮🇹
The code has been changed as described in the issue summary, and that is the correct way to fix the issue.
- 🇪🇬Egypt mahmoudsayed96 Cairo
Patch applied and issue fixed
Thanks @apaderno - Status changed to Fixed
about 1 year ago 5:54pm 14 December 2023 - Status changed to Fixed
about 1 year ago 5:57pm 14 December 2023