Anyone else having "Failed to Fetch" on GraphCool?

Hi guys sorry for this ultra noob question, is prisma the new graph.cool

is it made by the same people looking to replace graph.cool?

Also is there an authentication module, or a way to quickly implement auth services like in AppSync (AWS Amplify or Firebase)?

I think I don't like this new way of querying relation data Docs:

// A `main` function so that we can use async/await
async function main() {

  // Read the previously created user from the database and print their posts to the console
  const postsByUser = await prisma
    .user({ email: "<mailto:bob@prisma.io|bob@prisma.io>" })
    .posts()
  console.log(`All posts by that user: ${JSON.stringify(postsByUser)}`)

}

What if i wanted to query the posts and something else like books. How would i do that? would it require two round trip requests

const postsByUser = await prisma
    .user({ email: "<mailto:bob@prisma.io|bob@prisma.io>" })
    .posts()
const booksByUser = await prisma
    .user({ email: "<mailto:bob@prisma.io|bob@prisma.io>" })
    .books()

We loose the info way of only one query to get all data...

{
    id
    posts {
       id
    }
   books {
     id
   }
}

hi everyone

I was trying to follow various "official" tutorials provided by the old graphcool and new prisma, and found out that the packages and docs are pretty messy.

The Prisma team tries to push new thingy to the public while not announcing old stuff as deprecated.

Just as they abandoned graphcool in favor of prisma

Now, it seems that some boilerplates from a few months ago still used

prisma-binding

but new "official examples" are using

prisma-client

v1.17

Can someone please tell me what stack of tools should I use to start a new Prisma Project?

Hello everyone, I’m facing this very weird issue where I did the following: 1. Introduced a new optional Int field to an existing Prisma server 2. Now I want to run a manual migration by using “updateMany” mutation and I get an error “<field> is not defined in the input type” However, I can see that field defined in Playground. Moreover, I am able to run a regular update mutation (not a batch one) on a single item. Also, I am able to run this batch mutation with a local docker. Have any of you encountered this type of behaviour? This is really weird.

when running prisma locally via Docker

is it possible to connect to Postgres with a client?

I’ve forwarded the port, and used the credentials specified in the docker file

but I get connection refused

Hello everyone, does someone have experienced writing nested object write queries using go-client ? If so, can someone help me with a snippet ?There is the doc for typescript https://www.prisma.io/docs/prisma-client/basic-data-access/writing-data-TYPESCRIPT-rsc7/#nested-object-writes but not for golang.

I have an issue with paging not working correctly. I have a datamodel like

type User {
    id: ID! @unique
    numFollowers: Int! @default(value: "0")
}

I then try to run a query like:

return ctx.db.query.users({
                orderBy: "numFollowers_DESC",
                after: afterId,
                first: pageSize
            });

But if i run with an

afterId

that's not null I don't get valid results. I sometimes get duplicates, sometimes nothing

sorry I have a noob question in regards to prisma. We are migrating from graph.cool to prisma. Is it correct that we need to implement our own resolvers for prisma? Just wondering as in graph.cool this was abstracted away. Any help is much appreciated. Thanks

Hi! Do you know why npm shows 1.17.1 version while current stable is 1.17.2?

Just leave it here... https://www.prisma.io/forum/t/prisma-cms-boilerplate/4604

Woah! I’ve been happily paying $35/month for my graphcool subscription and suddenly this month it billed me for $450 because of the new way that pricing is calculated. @nilan who can I talk to about this please? I’ll have to immediately shut down my side project.

how can I do more powerful migrations with prisma? MIgrations that go beyond ranaming

Hey, so maybe this is just a general GraphQL question, but I'm trying to do some basic relations with Prisma. The relation is as follows: There is a table that stores Users and a table that stores Vehicles. A single Vehicle can belong to many Users, and each User can configure things like the display name of that Vehicle. So my schema looks like this:

type User {
  id: ID! @unique
  ...
  assets: [UserAsset!]!
}

type Asset {
  assetId: String! @unique
  assetType: AssetType
}

type UserAsset {
  asset: Asset!
  name: String!
}

Is this the proper way to go about something like this?

The problem is I'm finding it hard to do things like: "If an asset is deleted remove it from any users that have that asset"

ive deployed an app to digital ocean to learn but now my mutations are creating double entries in the db? this is the code https://github.com/zebapy/fs-prisma

Hi! I've been having an issue where I am trying to query all of something. Let's say users. such as:

export const userQueries = {
    async fetchUsers(_, {}, ctx) {
        console.log(await ctx.db.users())
        return ctx.db.users();
    }
};

but on playground it tells me:

"message": "Cannot return null for non-nullable field User.firstName.",

However, that

console.log

I have there does log out the object. Is there something I'm missing?

The angular boilerplate https://github.com/graphql-boilerplates/angular-fullstack-graphql says that it is outdated and points people to the react one. Any idea when it will be updated react and angular kinda two different frameworks... Update have notice that someone made a

pull-request

trying to update the code https://github.com/graphql-boilerplates/angular-fullstack-graphql/pull/140

Guys, what's going on with

graphql-yoga

? It's seems abandoned and not updated for months: https://github.com/prisma/graphql-yoga/issues/449

Is there a way to use the prisma client from nodejs directly instead of over the prisma cli?