* entc/gen: allow package with alias on ID field
* Update entc/gen/template/import.tmpl
Co-authored-by: Giau. Tran Minh <giau.tmg@gmail.com>
Co-authored-by: Giau. Tran Minh <giau.tmg@gmail.com>
* bumped pkg golang.org/x/tools version to address issue #2826
* .github: update go1.19 in go generate
Co-authored-by: Ankit Patial <ankitpatial@gmail.com>
* dialect/sql/builder: make sql.In() with empty args fallback to False()
* fix indent
* added comment
* remove the equilvalent logic in the codegen side
* comment fix, run go generate
* Fix problem when model maps integer id to a GoType
* Update generated files
* apply suggestions from code review
* Update generated files
* Update generated files after merge from master
* Cleanup test code in integration
Co-authored-by: Ariel Mashraki <7413593+a8m@users.noreply.github.com>
* Modify integration test IntSID.
Wrapped tests of IntSID for avoid conflicts.
* Modify tests in integrations
Order of tests was changed. As a result, if-statement for difference in RDB is deleted.
+ force pushing same commit to invoke ci.
Co-authored-by: Ariel Mashraki <7413593+a8m@users.noreply.github.com>
* fix(query): fix missing unique field in query builder template
when a query gets cloned the unique field doesn't get cloned
#2331
* fix(query): added missing go generate ./...
#2331
* fix(query): added missing go generate ./...
#2331
* fix: update only/onlyID comments
this patch updates the Only/OnlyID methods in the builder template from:
> // Returns a *NotSingularError when exactly one {{ $.Name }} entity is not found.
to
> // Returns a *NotSingularError when more than exactly one {{ $.Name }} ID is found.
in an effort to be more explicit in the explanation of the behavior of the methods.
* fix: update wording to be more concise from suggestion
Co-authored-by: Rotem Tamir <rotemtamir@gmail.com>
* fix: update Only wording to be more concicse
* fix: generate new files
Co-authored-by: Rotem Tamir <rotemtamir@gmail.com>
* Fix entql generation for ID types of Bytes, etc.
I was running into an issue trying to use a Bytes fieldas the ID field in a Schema, and it appears there is an currently an issue with using a Bytes field as the ID field in the entql codegen (it was outputing a function . I belive this should fix it (I tested this by adding the entql flag to the custom id integration test). I wasn't sure if the other cases I added (e.g. an ID field that is json type / time type / etc.) are actually sane ID field types, but if those don't make any sense I can remove some of those from the added conditionals.
* remove redundant line
Also, for some reason, the TimeMixin.UpdateTime was an immutable field,
but this was incorrent, because the codegen just skip generating
update setters to it. Removing the Immutable modifier allows users
to set this field explicitly.
