from: https://www.prisma.io/forum/t/access-connection-info-e-g-count-for-type-in-a-resolver/2522/3 this gives access to the count inside my resolver, but not as the result of my query?

let connection = await ctx.db.query.postsConnection(
  { },
  `{ aggregate { count } } }`,
)
let count = connection.aggregate.count

Hey guys, I’m having some trouble with returning nested information from a query located in my resolver. The line

const user = await ctx.db.query.user({ where: { id } })

is working as expected, but it’s not returning any nested data (in this case a nested type containing Stripe customer information is what I want to get back). These two nodes have a relation set up in my datamodel, and I’m correctly able to return the data using the same query in my playground. Am I missing something here? Why am I not able to get the nested data back in my resolver? And how else would I approach this, if it’s not doable?

is this the right slack for GraphCool-related questions? Anyway, one of my apps is still on legacy console, and it's no longer loading "system" data for "User" type

error reads:

Whoops. Looks like an internal server error.

out of curiosity, is anyone who has deployed

prisma

servers keeping track of operating costs?

I have mine running on GKE, and so far I'm sitting at about $20/m for a smaller solution. I'll most likely migrate to Digital Ocean when they open up their Kubernetes platform as I like DO more.

Under heavy load, and with horizontal scaling, it would probably scale to about $60, but at that point it'd be fine.

In my

BILLING

tab inside settings i always have

We're currently synchronizing your project data.

message. Is it quite a long process? 🙂

when seeding data, is it possible to use returned values?

for example, in my seed.graphql i have something like:

if that makes sense

i can do most of it with create/connect, but i've run into a couple cases where it would be much easier to use returned data like the id

Hey guys! I'm trying to figure out how to do user authentication with prisma cloud. Couldn't find any documentation. They way you would setup this with Graphcool was using functions like this:

but this doesn't work with prisma

can't find any documentation on how to edit prisma.yml for prisma cloud

Prisma deploy to heroku can you use mysql as datatype?

I’m having issues with graphql-yoga and prisma-binding I’m trying to write the a resolver to retrieve all

Users

, I have this resolver:

users: (_, args, context, info) => {
        console.log(info);
        return context.prisma.query.users({}, info);
    }

And when I hit the query I get this error:

Cannot return null for non-nullable field User.name.

The query looks like this:

{
  users {
    name
  }
}

Any idea on what I’m doing wrong?

Where is the documentation for the syntax used in the

where

object below?

homesInPriceRange: async (parent, args, ctx: Context, info) => {
    const where = {
      AND: [
        { pricing: { perNight_gte: args.min } },
        { pricing: { perNight_lte: args.max } },
      ],
    }
    return ctx.db.query.places({ where }, info)
  },

and the gql

aggregate

thingie below:

numRatings: {
    fragment: `fragment NumRatings on Place { id }`,
    resolve: async ({ id }, args, ctx: Context, info) => {
      const reviews = await ctx.db.query.reviewsConnection(
        { where: { place: { id } } },
        gql`{ aggregate { count } }`,
      )
      return reviews.aggregate.count
    },
  },

I have been looking for some kind of reference on when you can use

filter

or that you can use

min

and

max

on an Int? Is google no longer serving me or is the documentation on this stuff sparse?

running

prisma seed

is giving me

➜  lyra-api prisma seed

ERROR: Workspace * does not exist

{
  "data": {
    "generateClusterToken": null
  },
  "errors": [
    {
      "message": "Workspace * does not exist",
      "locations": [
        {
          "line": 3,
          "column": 9
        }
      ],
      "path": [
        "generateClusterToken"
      ],
      "code": 222
    }
  ],
  "status": 200
}

Get in touch if you need help: <https://www.prisma.io/forum/>
To get more detailed output, run $ export DEBUG="*"

Where does graphql-playground keep the application cache? I would like to clear the opened projects history

google showed other people with this error but it was fixed in older versions of the CLI, I just upgraded to the newest 😕

👋 Hello - had a quick question. If I am making a dedicated server for hosting a graphql API, and want to use the prisma API on the server as an ORM, do I need to deploy prisma to a separate server altogether? Or can I simply install it on my dedicated server?

I have such type:

type Action {
  id: ID! @unique
  title: String!
  date: String!
  description: String
  karma: String!
  executors: String!
  members: [ActionMember!]
  author: User!
}

And I get this error: The relation field

members

has the wrong format:

[ActionMember]

Possible Formats:

ActionMember

,

ActionMember!

,

[ActionMember!]!

Why can't I have

[ActionMember!]

? I want to make this field optional

Could somebody help me with this? I'm trying to solve this problem for a few days but I cannot find the solution :(( https://www.prisma.io/forum/t/i-get-wrong-result-after-mutation/3850

@Jenkins that's what I get when I use that schema

I have an update User mutation where the name, email and body are requried:

return ctx.db.mutation.updateUser(
  {
    where: { id },
    data: {
      name,
      email,
      body,
    },
  },
  info,
);

Is there a smart way to make the name, email and body optional, and only update them if a value has been passed? I could do it with some if statements but it makes my soul feel dirty:

if (name) {
	ctx.db.mutation.updateUser(
	  {
	    where: { id },
	    data: {
	      name,
	    },
	  },
	  info,
	);
}
if (email) {
	ctx.db.mutation.updateUser(
	  {
	    where: { id },
	    data: {
	      email,
	    },
	  },
	  info,
	);
}
if (body) {
	ctx.db.mutation.updateUser(
	  {
	    where: { id },
	    data: {
	      email,
	    },
	  },
	  info,
	);
}

Any chance this - https://github.com/prismagraphql/prisma/issues/2333 can be given a higher priority? Its been there for a while already, and its the only issue that prevents my project from operating properly. 🙏