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

GORM Playground Link

https://github.com/go-gorm/playground/pull/711 https://github.com/go-gorm/playground/pull/710

Description

This is related to https://github.com/go-gorm/gorm/issues/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')

Comment From: 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.

Comment From: gg1229505432

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