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
..
install
paginator
common.go
consistency.go
context_committer_test.go
context_test.go
context.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
convert.go
engine_test.go
engine.go
error.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
index_test.go
index.go
iterate_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
iterate.go
list_test.go	Use db.Find instead of writing methods for every object (#28084)	2023-11-24 03:49:41 +00:00
list.go	Use db.Find instead of writing methods for every object (#28084)	2023-11-24 03:49:41 +00:00
log.go
main_test.go
name.go
search.go
sequence.go
sql_postgres_with_schema.go