GSEC couldn't change user password after fix for CORE-3981 [CORE3986] #4318
Comments
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] |
|
Commented by: @dyemanov This patch cures the issue, but I'm not 100% sure in its correctness. I'd welcome any additional review. |
Modified by: @dyemanovAttachment: core-3986.patch [ 12263 ] |
|
Commented by: @asfernandes I'm not an expert on this part of the code, but, I don't understood why delete uses a parent_stream = 1 while store calls pass1_update (the first time) passing 0 (parent_stream). |
|
Commented by: @dmitry-starodubov It seems this patch fixes the problem. At least GSEC works again and QM tests performed without unexpected errors. |
|
Commented by: @dyemanov Besides the problems with deletes from updateable views mentioned by Adriano, I've found other issues with the original fix that are not addressed by the attached patch. So I'm investigating other solutions for the problem. |
Modified by: @dyemanovAttachment: core-3986.patch [ 12263 ] => |
|
Commented by: @dyemanov I've committed what I consider being a better patch. I don't assign a target version number as it's a snapshot only issue and it should not be included into the release notes for v2.5.3. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: @dmitry-starodubov
Is related to CORE3981
bin>gsec -user sysdba -pas masterkey -add test -pw test
bin>gsec -user sysdba -pas masterkey -mod test -pw test
An error occurred while attempting to modify the user record.
attempted update of read-only column
Commits: 60d8b9f 88bdceb
The text was updated successfully, but these errors were encountered: