Nanguan Lin d95102d650 Fix wrong xorm Delete usage (#27995) ... ## Bug in Gitea I ran into this bug when I accidentally used the wrong redirect URL for the oauth2 provider when using mssql. But the oauth2 provider still got added. Most of the time, we use `Delete(&some{id: some.id})` or `In(condition).Delete(&some{})`, which specify the conditions. But the function uses `Delete(source)` when `source.Cfg` is a `TEXT` field and not empty. This will cause xorm `Delete` function not working in mssql. 61ff91f960/models/auth/source.go (L234-L240) ## Reason Because the `TEXT` field can not be compared in mssql, xorm doesn't support it according to [this PR](https://gitea.com/xorm/xorm/pulls/2062) [related code](b23798dc98/internal/statements/statement.go (L552-L558)) in xorm ```go if statement.dialect.URI().DBType == schemas.MSSQL && (col.SQLType.Name == schemas.Text ||   col.SQLType.IsBlob() || col.SQLType.Name == schemas.TimeStampz) {   if utils.IsValueZero(fieldValue) {   continue   }   return nil, fmt.Errorf("column %s is a TEXT type with data %#v which cannot be as compare condition", col.Name, fieldValue.Interface())   } } ``` When using the `Delete` function in xorm, the non-empty fields will auto-set as conditions(perhaps some special fields are not?). If `TEXT` field is not empty, xorm will return an error. I only found this usage after searching, but maybe there is something I missing. --------- Co-authored-by: delvh <dev.lh@web.de>		2023-11-12 07:38:45 +00:00
..
access_token_scope_test.go
access_token_scope.go
access_token_test.go
access_token.go
auth_token.go
main_test.go
oauth2_test.go
oauth2.go
session.go
source_test.go
source.go	Fix wrong xorm Delete usage (#27995)	2023-11-12 07:38:45 +00:00
twofactor.go
webauthn_test.go
webauthn.go