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
..
appstate.go	Replace more db.DefaultContext (#27628)	2023-10-15 17:46:06 +02:00
main_test.go	make writing main test easier (#27270)	2023-09-28 01:38:53 +00:00
notice.go	Even more db.DefaultContext refactor (#27352)	2023-10-03 10:30:41 +00:00
notice_test.go	Even more db.DefaultContext refactor (#27352)	2023-10-03 10:30:41 +00:00
setting.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
setting_test.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