qe: start introducing typed identifiers in relations #3672
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tomhoule
commented
Feb 6, 2023
| /// to be rendered as comments. Since the parser will not set these flags when reading a schema | ||
| /// string, only introspection and the lowering of the datamodel to the ast care about these flags. | ||
| /// The FieldType: Unsupported behaves in the same way. | ||
| /// Both of these are never converted into the internal datamodel. |
There was a problem hiding this comment.
This is not accurate anymore.
tomhoule
force-pushed
the
qe-typed-identifiers-relations
branch
from
5a7886e to
305e470
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
part of https://github.com/prisma/team-orm/issues/13