* 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
Also, added additional example where an edge schema has another edge
to a type that holds an information about the relationship.
The only reason this example exists is to allow users to reduce the storage
occupied by the join-table and allow connect (via M2O) multiple edge-schemas
to an 'information'/'description' node.
* 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>
* dialect/sql/schema: file based type store
This PR adds support for a file based type storage when using versioned migrations. The file called `.ent_types` is written to the migration directory alongside the migration files and will be kept in sync for every migration file generation run.
In order to not break existing code, where the type storage might differ for different deployment, global unique ID mut be enabled by using a new option. This will also be raised as an error to the user when attempting to use versioned migrations and global unique ID.
Documentation will be added to this PR once feedback on the code is gathered.
* apply CR
* fix tests
* change format of types file to exclude it from atlas.sum file
* docs and drift test
* apply CR
* replace default field comment with user comment if defined
* use comments defined on edges in generated entities
* add docs for comment method on edges and fields
* update integration to reflect above changes
This will allow us to store information about pk ranges allocated per type in a different location thant the database. This is useful for deterministic pk range computation for things like generating atlas.hcl out of the Ent schema.
