v0.3.0 #113
RobertCraigie
started this conversation in
General
v0.3.0
#113
Replies: 1 comment 1 reply
-
getting same error |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Breaking Changes
The
prisma
field name is now reserved, trying to generate a model that has a field calledprisma
will raise an error.You can, however, still create a model that uses the
prisma
field name at the database level.What's Changed
Querying from Model Classes
You can now run prisma queries directly from model classes, for example:
This API is exactly the same as the previous client-based API.
To get starting running queries from model classes, you must first register the prisma client instance that will be used to communicate with the database.
For more details, visit the documentation.
Count non-null fields
You can now select which fields are returned by
count()
.This returns a dictionary matching the fields that are passed in the
select
argument.Support for Python 3.10
Python 3.10 is now officially supported.
Prisma Update
The internal Prisma binaries that Prisma Client Python uses have been upgraded from
3.3.0
to3.4.0
.prisma db push
support for MongoDBImproved Client Generation Message
The current version of the client will now be displayed post-generation:
Improved Generation Error Message
An explicit and helpful message is now shown when attempting to generate the Python Client using an unexpected version of Prisma.
Other Changes
--type-depth
option toprisma py generate
This discussion was created from the release v0.3.0.
Beta Was this translation helpful? Give feedback.
All reactions