Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

keep database specific fields #179

Open
maxswjeon opened this issue Feb 21, 2023 · 1 comment
Open

keep database specific fields #179

maxswjeon opened this issue Feb 21, 2023 · 1 comment

Comments

@maxswjeon
Copy link

Currently, the database specific fields (such as @db.Timestamp(6) or @db.Uuid()) is removed after transform. Is there any way to keep them?
@aniravi24
Copy link
Contributor

I was looking around to see if they provide that information in their API, but it looks like Prisma doesn't return this information in their API yet.

This package is built on the DMMF API from Prisma but the DMMF doesn't contain the native type attribute info.

prisma/prisma#10252

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aniravi24 @maxswjeon