Behavior of .Not(Where().Or()) has changed

[tsurunoyu]

GORM Playground Link

go-gorm/playground#711
go-gorm/playground#710

Description

This is related to #6845.

The behavior of .Not(DB.Where().Or()) has changed.

In the sample code,

for v1.25.5, the playground code produces: WHERE NOT (name = 'a' OR name = 'b')
for master, the playground code produces: WHERE NOT (name = 'a' AND name = 'b')

[albert-anzenna]

@jinzhu and @gg1229505432 any updates on this issue? We are aware of this issue and we think this issue was not fixed in the quoted commits.

[gg1229505432]

I'm not being pulled into the contributor list, so I don't have permission to merge code 🧐