Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support datasource-specific attributes
See original GitHub issueProblem
Databases like Postgres are incredibly feature-rich. Exposing all of those features would clutter up the schema for databases that do not support these features.
Possible Solution
We introduce datasource-specific attributes @pg.check(...), which allow more advanced features while making it clear that this is datasource-specific and may make it harder to switch databases.
Original Question
Where are the pg attributes documented? For example I want to specify the maximum length of a string or customize the type definition for postgres, it’s hard to find out what is available.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@janpio
The specific directives are also not documented(https://github.com/prisma/prisma2/tree/master/docs) so I added that label as well so that once they are implemented we need to document them as well.
This is now supported via native types, including a catch-call notation for types we don’t yet support. The feature request described in this issue is pretty generic, so I am closing it.
For native types beyond the supported ones, we would like to have specific types requested (Postgis, Interval, etc.). for other features, e.g. database views, or stored procedures specific feature requests also welcome.
Make sure to check out https://www.prisma.io/docs/concepts/components/preview-features/native-types