However the built-in graphql api

where:{ title_contains }

does not provide case-insensitive search, and I cant perform raw sql queries with Client neither.

So, how do you guys implement search with prisma client?

Hi, we're having problems trying to change a database password on one of our servers. The issue is that we don't know where/what the current MySQL password that was set at the time. We can easily change our password on our end, but how do we modify the database password on prisma? This is currently giving us issues, and it's quite painful.

Hi Everyone, we are a North Carolina company, called ScoreShots. We are on a paid tier but having a devil of a time getting any reply from technical support. Does anyone have any advice for how to contact support? Many thanks, y'all.

Hi guys. I’ve searched something about import types from

.graphql

files. I’ve found [graphql-import](https://github.com/prisma/graphql-import) to import using

# import something from 'something-else'

. This works fine between

.graphql

files. But what I’m trying to do is to import some

types

from

generated.graphql

from Prisma into a

.js

file. For example: I have this

generated.graphql

file from Prisma

graphql
"""generated.graphql file"""
type ItemWhereInput { ... }

type ItemConnection { ... }

...

I would like to import some types from

generated.graphql

file to

items-types.js

file

javascript
// items-types.js file

import gql from 'graphql-tag';
// I would like to make some kind of import ItemWhereInput and ItemConnection here
// Something like `import { ItemWhereInput, ItemConnection } from 'generated.graphql'`

... 

const ItemWhereUniqueInput = gql`
  input ItemWhereUniqueInput {
    id: String!
  }
`;

... 

// And export ItemWhereInput and ItemConnection here
export default [Item, ItemInput, ItemWhereUniqueInput, ItemUpdateInput];

That way I could call

makeExecutableSchema

from

graphql-tools

and use those types in some place else

javascript
// items-query.js file

import { forwardTo } from 'prisma-binding';

const schema = `
  items: [Item]!
  item (where: ItemWhereUniqueInput!): Item
  
  # And use it here
  itemsConnection (where: ItemWhereInput): ItemConnection!
`;

const resolvers = {
  items: forwardTo('db'),
  item: forwardTo('db'),
  itemsConnection: forwardTo('db'),
};

export default {
  schema,
  resolvers,
};

If it is somewhere else or there are something that could help, please, point me out. Thanks ahead

I really wish Prisma CLI would stop getting stuck on applying change 2 of 1

Like… of course you cannot apply the second change of a set of one change, and yet:

Changes:

  PortalCart (Type)
  ~ Updated field `owner`

Applying changes (2/1) ⣯

Hi all, I think I have found a bug in the Typescript client, but wanted to ask here if I am doing things right before I go to the trouble of opening an issue. I have the code here:``` notifications: { subscribe: async (root, args, context: IntResolverContext, info): Promise<AsyncIterator<Notification>> => { const { db, id } = context; return db.$subscribe.notification({ where: { AND: [ { mutation_in: ["CREATED"] }, // the notification was just created, rather than updated or deleted { node: { user: { id, // filter for notifications where the user has the current id }, }, }, ], }, // typescript seems to be broken here 😠 } as any).node(); }, },

If I don't cast the argument `any` then I get the error ```Argument of type '{ where: { AND: ({ mutation_in: string[]; } | { node: { user: { id: string; }; }; })[]; }; }' is not assignable to parameter of type 'NotificationSubscriptionWhereInput'.
  Object literal may only specify known properties, and 'where' does not exist in type 'NotificationSubscriptionWhereInput'

The code works as it is now even with the error. If I take away the

where

property, and just make the

AND

as the first key then I get no typescript error but the code will not work. Maybe the generated types are incorrect? Also possible I'm just using the library wrong.

anyone know why when deploying to an existing schema, prisma responds that it did the migration, but it’s schema didn’t change?

Can confirm that logs in prisma cluster say it happened, and mysql is updated.

Just the responding prisma schema is wrong

after a cluster restart it came up

Ahh we had a rabbitmq failure, that was causing schema not to propagate across cluster

Hi, where should we ask questions?

Coming from discord...

Any one know if you can set the

createdAt: DateTime!

and

updatedAt: DateTime!

values by Seeding or Import your data? I’m trying to write a parser that is importing data from other data sources and it would be nice not to have to make a ‘created_at’, and ‘updated_at’ property…

Hi all, with prisma client, how to return the entire SubscriptionPayload by example

type PostSubscriptionPayload {
  mutation: MutationType!
  node: Post
  updatedFields: [String!]
  previousValues: PostPreviousValues
}

from one subscription like

type Subscription {
  posts: PostSubscriptionPayload
}

? I tried this:

posts: {
    subscribe: async (parent, args, ctx) => {
      return ctx.prisma.$<http://subscribe.post|subscribe.post>()
    },
    resolve: payload => {
      console.log(payload)
      return payload
    }
  }

But in the resolve function I receive only the mutation Type, all others fields are null, whatever is the mutation type.

In prisma.yml, when we do "${env:PRISMA_ENDPOINT}", where does that syntax come from? What parses the ${env:something} and what else can we do with it?

Is it possible to migrate an existing database to Prisma cloud?

Hi all, I'd like to ask you guys if you know how to disable logs on graphql-yoga on production. I'm talking about this kind of logs. I tried

debug:false

on server options but it didn't have any effect. Thank you.

Hi, not sure if this is the correct channel to discuss this, but I am having issues with typegql

despite decorating

@InputField{isNullable:true})

my mutation still expects all params as required.

I set the

?

optional type on typescript but still does not work

hello everyone, I have graphql schema type of User in which I have a field of follower , in which I want to define a list of User types . when I am doing this and deploy to prisma , it showing me other possible type and none of which are working and showing error

if wrong how to define a field which return list of its parent Type

So I'm getting an

You must wrap the query string in a "gql" tag.

error when calling refreshQueries. What am I overlooking here? pagination.js

const PAGINATION_QUERY = gql`
    query PAGINATION_QUERY {
        itemsConnection {
            aggregate {
                count
            }
        }
    }
`;

export { PAGINATION_QUERY };

createItem.js

import deleteItemsFromCache from '../utils/deleteItemsFromCache';
import PAGINATION_QUERY from './Pagination';

update = (cache, payload) => {
    deleteItemsFromCache
};

<Mutation 
    mutation={CREATE_ITEM_MUTATION} 
    variables={this.state}
    update={this.update}
    refetchQueries={[{ query: PAGINATION_QUERY }]}
>

Hi guys, so i’m just trying to play around with Heroku deployment by seeing if i can deploy one of the example applications specifically node-graphql-auth.

I really think there is a big problem with prisma client and subscription: First problem I notice is there is actually no way to return directly the full subscription payload like

type PostSubscriptionPayload {
  mutation: MutationType!
  node: Post
  updatedFields: [String!]
  previousValues: PostPreviousValues
}

Because when I try with something like that in the resolver

return ...prisma.$<http://subscribe.post|subscribe.post>()

and I console log the returned payload of this, I get

PostSubscriptionPayload

but only

updatedFields

and

mutation

fields are set correctly, the other fields remains null, whatever is the event (creation, delete, update). Second problem, and this is a big one because it concerns the DELETE subscription, we can't get back the previous value of the deleted node at all! If I try

ctx.prisma.$<http://subscribe.post|subscribe.post>({ mutation_in: ['DELETED'] }).previousValues()

with

type Subscription {
  deletedPost: PostPreviousValues! // I tested with Post! too, same error
}

I get

null

Note that I console log the payload in the

resolve

function of each subscription resolver like

deletedPost: {
    subscribe: async (parent, args, ctx) => {
      return ctx.prisma.$<http://subscribe.post|subscribe.post>({ mutation_in: ['DELETED'] }).previousValues()
    },
    resolve: payload => {
      console.log(payload)
      return payload
    }
  }

So I'm pretty sure the problem comes from prisma Client 🤪 prisma 1.19 (docker image as well)

Hi guys, I've set-up a GraphQL Server using Prisma, graphql-yoga and some other packages. Now I wish to start using the api in a client application. Is there any plugin/method to have autocompletion/validation in VSCode when writing queries / mutations within the gql`...` tags based on the graphql schema?

Hi, Im trying to deploy prisma server on aws fargate ( following this tutorial: https://www.prisma.io/docs/tutorials/deploy-prisma-servers/aws-fargate-joofei3ahd/#2.-deploying-a-prisma-server-to-fargate ) but when trying to deploy AWS Fargate Prisma stack. I keep getting the following error: Unable to assume the service linked role. Please verify that the ECS service linked role exists. (Service: AmazonECS; Status Code: 400; Error Code: InvalidParameterException; Any suggestions? Thanks