Am I the only one having issues with

OR

is the where variable?

I'm getting errors that its undefined

Hi guys, anybody having issues using the

prisma login --key {SESSION_KEY}

in prisma-cli? It still opens the browser for me, which makes my CI/CD build fail.

Hi I have a question: is there anyway in prisma to setup events/listeners like in typeORM (https://typeorm.io/#/listeners-and-subscribers) ? I've seen some directives like

@createdAt

and

@updatedAt

but nothing more a part of this. A use case might to encrypt a password before update always like this implementation for mongoose:

UserSchema.pre("save", function(next) {
    this.password = Bcrypt.hashSync(this.password, 10);
    next();
});

thx in advance 🙂

The filter

OR

is not working for me even after copying the exact example from the docs:

const filteredPosts: Post[] = await prisma.posts({
  where: {
    OR: [
      {
        title_contains: 'graphql',
      },
      {
        title_contains: 'prisma',
      },
    ],
    createdAt_gt: '2018',
    createdAt_lt: '2020',
  },
})

where

alone works with one condition but keep getting errors that

OR

does not exist

Hi i have a question regarding prisma-client-typescript i get a babel error on runtime. I’m unable to resolve why this is happening. Syntax error …generated/prisma-client/index.ts: Unexpected token (9:12)

Hey guys, does anyone know when we can expect subscription support for Prisma 2?

Can I use id in numerical form auto increment?

What is the use of the

info

resolver argument? Howtographql does not elaborate on that

How can I filter a set of items which have a DateTime field to only retrieve items in between two provided dates?

are there any docs about system requirments for prisma? I searched docs for “RAM” and “GB” but not zero results.

found some mentions in the issues, but is there nothing official?

Does prisma (1+2) rely on IDs being globally unique (like in dataloader, cache etc.)? The reason I'm asking is that we are moving legacy data to prisma 1 using

prisma import

which enables us to retain the legacy datas IDs, but they are not globally unique. Are there any tripwires we should be aware of in this regard?

Still getting used to working with Prisma, but as I haven’t already just wanted to say a huge shout out to all you guys working on Prisma and Prisma 2 - really incredible work. Thank you!

How do I create a relation between two items when creating a new one? I wanna connect one item to one user and I would like to identify the user with his email. I added the email as an unique field to the datamodel and added the connection like that:

user: {
          connect: {
            email: args.email
          }
        }

Is that not sufficient? I receive the following error: Field value.user of required type UserCreateOneInput! was not provided. When I check the generated file I see:

input UserWhereUniqueInput {
  id: ID
  email: String
}

For me that means that I can either identify the user through his id or his email, or do I understand something, perhaps the error, wrong?

I think the error is related with typescript and how you are writing the resolver

some arguments seems not to be correct

Inside the resolver I receive the appropriate arguments I need for the creation, so I think the GraphQL part here is correct. Maybe the syntax I use to create the item is wrong?

const item = await ctx.db.mutation.createItem(
      {
        user: {
          connect: {
            email: args.email
          }
        },
        data: { title: args.title }
      },
      info
    );

The type:

type Item {
  id: ID! @id
  title: String!
  createdAt: DateTime! @createdAt
  updatedAt: DateTime! @updatedAt
  user: User!
}

Oh well, I nested it wrong. The connection to the user is supposed to be inside of the data key 🤦‍♂️

Hey I am new to Prisma anyone help I am trying to create user mutation via react-apollo but its not working, I came across an error and I do not know how to fix it. The error says: 'Uncaught (in promise) Error: GraphQL error: Unknown argument 'firstName' on field 'createStudent' of type 'Mutation'. (line 2, column 17): createStudent(firstName: $firstName, lastName: $lastName, studentNumber: $studentNumber, contact: $contact, password: $password) {'

I will be in Vietnam - Saigon next week - any fan of Prisma around let's have a coffee

hello guys I keep getting this error on my browser and CMD

Field "id" is not defined by type SubCategoryCreateOneWithoutItemsInput at value.subCategory

I am using Nextjs, Apollo, Graphql Yoga with Prisma and my schema is

type Mutation {
  createItem(
    title: String
    description: String
    price: Int
    image: String
    subCategory: SubCategoryInput
    published: Boolean
  ): Item!
}

input SubCategoryInput {
  id: ID!
  name: String
  body: String
  image: String
  items: [ItemInput]
  category: CategoryInput
}

Anyone uses TypeScript with Prisma? I am doing:

const user: IUser = await db.query.user(
    { where: { id: req.userId } },
    '{ id, permissions, email, name }'
  );

And I just recently moved my prisma import to from

const { Prisma } = require('prisma-binding');

to

import { Prisma } from 'prisma-binding';

Now I receive a type error, stating that the second argument to my user function (basically

'{ id, permissions, email, name }'

) has the wrong type and is not of type

[key: string]: any;

. The types are coming, for whatever reason, from graphql-bindings -- and are defined as the following:

export interface QueryMap {
    [rootField: string]: (args?: {
        [key: string]: any;
    }, context?: {
        [key: string]: any;
    }, info?: GraphQLResolveInfo | string) => Promise<any>;
}

So I think the object I am providing is supposed to be the info object but I couldn't imagine that the syntax or the parameter order changes due to the switch to typescript... 🤔

Whew... what a ride. Why can I not use the User type exported from the generated client as a type for a variable when using await? It says it then misses things like then(). Basically I am doing:

const user: User = await prisma.user({ id: req.userId });

where User is:

import { User } from './generated/prisma-client';

. It results in:

Type 'UserNode' is missing the following properties from type 'User': then, catch, [Symbol.toStringTag], finally, $fragment

All the examples are working like that tho, see: https://codesandbox.io/s/x7o68w0pzp?module=%2Fsrc%2Freading-data%2Flists-and-single-objects.ts Line 14

Plus can I not pass the info object to prisma.user to only retrieve certain fields (when using graphql)?