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
..
check_test.go	Replace assert.Fail with assert.FailNow (#27578)	2023-10-11 11:02:24 +00:00
check.go	Penultimate round of db.DefaultContext refactor (#27414)	2023-10-11 04:24:07 +00:00
comment.go
commit_status.go
edits.go
lfs.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
main_test.go
merge_merge.go
merge_prepare.go
merge_rebase.go
merge_squash.go
merge_test.go
merge.go	Fix poster is not loaded in get default merge message (#27657)	2023-10-17 15:07:23 +00:00
patch_unmerged.go
patch.go
pull_test.go
pull.go	Final round of db.DefaultContext refactor (#27587)	2023-10-14 08:37:24 +00:00
review.go	Use db.Find instead of writing methods for every object (#28084)	2023-11-24 03:49:41 +00:00
temp_repo.go
update_rebase.go
update.go