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
..
cherry_pick.go
commit.go
content.go
content_test.go	make writing main test easier (#27270)	2023-09-28 01:38:53 +00:00
diff.go
diff_test.go
file.go
file_test.go
patch.go	Updates to the API for archived repos (#27149)	2023-09-21 23:43:29 +00:00
temp_repo.go	Upgrade to golangci-lint@v1.55.0 (#27756)	2023-10-24 02:54:59 +00:00
tree.go
tree_test.go
update.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
upload.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