Assets
2
Bugfixes:
- #2847 : follow up bugfix for malformed previous values in subscription results for delete events
- #2536, #2906: deploy got stuck when renaming a relation
- #2793: perform detection of duplicate types and fields in a case insensitive way
- #3198: changing the type of a required scalar field must error if there are nodes
- #2953: Fixed a bug where Cascading Delete would fail if more than 32768 nodes in one table where affected.
- #2927: changing an optional field to required ignored casing and crashed
- #2871 #3239 : make schema validation more resilient and do not crash when encountering unexpected errors
Assets
2
Changes
BREAKING: Go Client Rewrite
This version includes the rewritten Go client with many Go idiomatic API changes to the generated client #3278
Make client connections lazy
This versions fixes a bug in all JS based Prisma client implementations that wouldn't allow a CLI app to close because client initiated long running connections eagerly. The fix makes the connection happen lazily.
Prisma init and generate workflow
This version makes a few changes to the init workflow:-
- The interactive prisma init wizard now invokes generate so that the client is already initially generated
- Changes the default path of output client in generated prisma.yml to
output: ./generated/prisma-client/ - Removes the post-deploy hook from generated prisma.yml file
Detect prisma.yml additionally in prisma/prisma.yml
This version looks for prisma.yml in three places (in order)
- prisma.yml in current directory
- prisma.yml in ./prisma/prisma.yml
- prisma.yml path from graphql config
The step 2 is added as a feature in this version.
BREAKING: Remove forwardTo from Prisma client
This version removes forwardTo from Prisma client. This feature relies on schema delegation and we recommend using prisma-binding for that.
Assets
2
Other
- BREAKING: one relation fields on a type used to include a where argument. This argument has been removed now as it was not intended to be part of the API in the first place. Here is an example:
# before the change
type Todo implements Node {
id: ID!
title: String!
user(where: UserWhereInput): User!
}
# after the change
type Todo implements Node {
id: ID!
title: String!
user: User!
}
Assets
2
Bugfixes:
- using
updatedFields_containsandmutation_inat the same time breaks subscription queries (#2333) - exporting Json Lists and importing them again did not work since the export would stringify the lists and the CLI validation would then reject this format. This is now fixed by not stringifying the json lists during export. (#3168)
Assets
2
Due to a bug in our publish script, we release this patch.
Assets
2
Changes
- BREAKING: one relation fields on a type used to include a where argument. This argument has been removed now as it was not intended to be part of the API in the first place. Here is an example:
before the change
type Todo implements Node {
id: ID!
title: String!
user(where: UserWhereInput): User!
}after the change
type Todo implements Node {
id: ID!
title: String!
user: User!
}
Assets
2
Changes
cluster, service, stage and schema final removal
This version doesn't support the cluster, service, stage and schema properties anymore. The cluster, service and stage properties are being replaced by endpoint, as already announced in 1.7.
Prisma Client & generate command
This release includes the new Prisma Client. The Prisma Client is a generated client for the languages JavaScript, TypeScript, Flow and Go. It can be generated by adding a generate property to the prisma.yml:
datamodel: datamodel.graphql
endpoint: http://localhost:4466
generate:
- generator: typescript-client
output: ./src/generated/prisma
With the prisma generate command, the client will now be generated and can be used like this:
import { prisma } from './generated/prisma'
const uersers = await prisma.users()
Raw database access fallback
Prisma exposes a flexible API that conforms to the OpenCRUD specification.
This API has excellent developer ergonomics and is powerful enough to cover most use cases. Sometimes, however you need to drop down to the native API of the underlying database to perform a more complex operation. This raw access feature has been implemented now (#2052). This feature is available in the executeRaw mutation:
mutation {
executeRaw(
database: default,
query: "SELECT TOP(10) FROM Users ORDER BY uuid()"
)
}
Assets
2
Changes
Bugfixes
- Fix a bug in the Postgres Connector where using a field in the orderBy that is not part of the selected set leads to an error #3156
Assets
2
Changes
Bugfixes
- Fix a bug in the Postgres Connector where first and last were not working as intended when nested #3127
Assets
2
Changes
Bugfixes
- improve logic for handling multiple different fragments for one field (follow up for #2995)