Lunny Xiao dd30d9d5c0 Remove GetByBean method because sometimes it's danger when query condition parameter is zero and also introduce new generic methods (#28220) ... The function `GetByBean` has an obvious defect that when the fields are empty values, it will be ignored. Then users will get a wrong result which is possibly used to make a security problem. To avoid the possibility, this PR removed function `GetByBean` and all references. And some new generic functions have been introduced to be used. The recommand usage like below. ```go // if query an object according id obj, err := db.GetByID[Object](ctx, id) // query with other conditions obj, err := db.Get[Object](ctx, builder.Eq{"a": a, "b":b}) ```		2023-12-07 15:27:36 +08:00
..
avatar.go	Replace -1 with GhostUserID (#27703)	2023-10-20 14:43:08 +00:00
badge.go
email_address.go	Remove GetByBean method because sometimes it's danger when query condition parameter is zero and also introduce new generic methods (#28220)	2023-12-07 15:27:36 +08:00
email_address_test.go
error.go
external_login_user.go	Remove GetByBean method because sometimes it's danger when query condition parameter is zero and also introduce new generic methods (#28220)	2023-12-07 15:27:36 +08:00
follow.go
follow_test.go
list.go
main_test.go
must_change_password.go
openid.go
openid_test.go
redirect.go
redirect_test.go
search.go
setting.go
setting_keys.go
setting_test.go
user.go	Replace -1 with GhostUserID (#27703)	2023-10-20 14:43:08 +00:00
user_system.go	Replace -1 with GhostUserID (#27703)	2023-10-20 14:43:08 +00:00
user_test.go
user_update.go