Ola Okelola
Ola Okelola
there's dependencies we use for graphql scalars but it's not expressed anywhere and we need a better way of indicating this * `JSONType` or `JSONBType`: `graphql-type-json` * `BinaryTextType` or `ByteaType`:...
`.ent/history` maybe? how far should we go? command run, git branch, timestamp, alembic changes are all possible candidates for this edges created or removed
if a change is made and downgraded without committing to source control and then we see a reference to it later, it's very hard to debug what happened ``` auto_schema...
It only works for edges that are in their own table TODO in code still needs to be addressed: https://github.com/lolopinto/ent/blob/master/internal/db/db_schema.go#L491 partial indices probably what we want here: https://www.postgresql.org/docs/current/indexes-partial.html never finished...
EntQuery will help a lot but we need a way for this to be handled by default and to be customized for each edge and/or project
e.g. max number of invites to a group a user can send etc
very specific case of https://github.com/lolopinto/ent/issues/1548 e.g. pgvector, postgis etc
we don't support all types and we need the ability for people to use one of the non-supported types and a way to configure * db * graphql * typescript...
``` These forms set or remove the default value for a column. Note that defaults only apply to subsequent INSERT commands; they do not cause rows already in the table...