How would I go about fixing the errors?

I'm unfortunately unable to attend GraphQL conf this week, willing to sell my ticket for the early bird price €200 if anyone is interested

Hi folks, quick question: when using Relay client-side, is it mandatory to implement edges and nodes for relationships in the API scheme? If not, I’m trying to figure out how to manipulate the store in a Relay (optimistic) updater without them.

Anyone having an issue with graphqlgen since updating Prisma?

I am trying to connect to postgresql database and when i am trying to run “prisma deploy” it is giving me error: Could not connect to server at http://localhost:4466/. Please check if your server is running. After i checked my docket container and it is restarting again and again(Running on Centos 7). Here are the logs of the container: prisma_1 | No log level set, defaulting to INFO. prisma_1 | [INFO] {} - Started. prisma_1 | Exception in thread "main" org.postgresql.util.PSQLException: ERROR: syntax error at or near "NOT" prisma_1 | Position: 18 prisma_1 | at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2433) prisma_1 | at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2178) prisma_1 | at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:306) prisma_1 | at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:441) prisma_1 | at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:365) prisma_1 | at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:155) prisma_1 | at org.postgresql.jdbc.PgPreparedStatement.execute(PgPreparedStatement.java:144) prisma_1 | at slick.jdbc.StatementInvoker.results(StatementInvoker.scala:38) prisma_1 | at slick.jdbc.StatementInvoker.iteratorTo(StatementInvoker.scala:21) prisma_1 | at slick.jdbc.Invoker.first(Invoker.scala:30) prisma_1 | at slick.jdbc.Invoker.first$(Invoker.scala:29) prisma_1 | at slick.jdbc.StatementInvoker.first(StatementInvoker.scala:15) prisma_1 | at slick.jdbc.StreamingInvokerAction$HeadAction.run(StreamingInvokerAction.scala:52) prisma_1 | at slick.jdbc.StreamingInvokerAction$HeadAction.run(StreamingInvokerAction.scala:51) prisma_1 | at Please help.

Are the Prisma Day talks going to be live-streamed, or will the videos be made available afterwards?

Anyone live on the chat right now? I sure could use some help in understanding a Prisma concept.

Anyone have any luck using prisma in conjunction with https://github.com/zombodb/zombodb ?

Hey, just wanted to give a shout out to @devendradhanal… the dude rocks.

are people here experiencing slow response times with Prisma when grabbing relations? I have a relatively simple query like this:

query Stores {
  searchLocalBusinesses(
    where: { aroundGeolocation: "u3buwmf", aroundRadius: 7000 }
  ) {
    nodes {
      id
      vampireSquidId
      name
      streetAddress
      postalCode
      city
      longitude
      latitude
      externalId
      business {
        countryCode
        name
        vampireSquidId
        positiveLogotype {
          url(width: 160, height: 45)
        }
        negativeLogotype {
          url(width: 160, height: 45)
        }
        primaryColor
        websiteLink
        shortDescription
      }
    }
  }
}

when load testing this with wrk I get these results:

└─ $ ▶ LT_DURATION=30s LT_CONNS=30 LT_THREADS=4 wrk -t4 -d30s -c30 '--latency' --script local-business-search.lua --timeout 2s "<http://localhost:4000/v3>"
Running 30s test @ <http://localhost:4000/v3>
  4 threads and 30 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     1.25s   220.43ms   1.83s    65.55%
    Req/Sec     7.54      5.67    30.00     82.91%
  Latency Distribution
     50%    1.24s
     75%    1.41s
     90%    1.56s
     99%    1.76s
  659 requests in 30.09s, 16.30MB read
Requests/sec:     21.90
Transfer/sec:    554.58KB

in other words, very low throughput and slow response times. and it's all due to

business

,

business.positiveLogotype

and

business.negativeLogotype

. I thought Prisma was going to be fast using data pooling but my tests don't reflect that. are there any tricks to this? my resolver look like this:

module.exports = async (root, args, ctx) => {
    const t = Date.now();
    const result = await searchLocalBusiness(args);
    console.log('es search', Date.now() - t);
    const tt = Date.now();
    const nodes = await ctx.prisma.localBusinesses({where: {id_in: result.ids}});

    console.log('hydrate', Date.now() - tt);

    return {
        total: result.total,
        took: result.took,
        nodes: nodes,
        pageInfo: pageInfo(args, result.total, nodes.length, 10000)
    };
};

it's basically the opposite of what https://www.prisma.io/features/query-engine is saying.

hydrate

is taking all the time and it becomes slower and slower where elasticsearch is consistently fast. ES takes around 30ms and hydrate 400ms

hello guys. is there anyway to groupby in Prisma ?

I’m trying to create a Table relation like the example in the docs

type User {
  id: ID! @id
  posts: [Post!]!
}

type Post {
  id: ID! @id
  user: User! @relation(link: TABLE, name: "MyRelation")
}

type MyRelation @relationTable {
  user: User!
  post: Post!
}

but when I try to deploy, I get this

You are trying to set the relation 'MyRelation' from `Post` to `User` and are only providing a relation directive with a name on `Post`. Please also provide the same named relation directive on the relation field on `User` pointing towards `Post`.

why is that? I’m using mySQL

I’m using prisma v 1.34

Waiting for the first guide/boilerplate on Prisma 2 🙂

I just tried the new prisma2 commands, I can connect to my db with the prisma2 init command, but the introspection of the database did not work (MySQL), is it supposed to?

We would like to give our client access to prisma admin. Is there a way to authenticate without using the secret token?

I won't be able to attend Prisma Day in Berlin. Will there be recordings of the talks that day posted online? Really want to see what's new and coming..

Hey there. Anyone working with Prisma and multiple user profiles (each having a different type and resolvers)? What approach are you using?

why? 😐

Prisma 2 is great so far, when will the life-cycle hooks be implemented? That's what I'm looking forward to the most

Hey everyone, running into an issue when using

prisma deploy

using an introspected Postgres schema, similar to this issue https://github.com/prisma/prisma/issues/4473

com.prisma.shared.models.TypeIdentifier$Relation$ cannot be cast to com.prisma.shared.models.TypeIdentifier$ScalarTypeIdentifier

Do you know how I go about debugging please?

Will prisma day be streamed online anywhere?

Enjoy Prisma Day today! I wish I could be there!

Is there a downside with using the prisma library instead of the standalone server? My understanding was the server is stateful and has cache for frequent queries as they occur. I have quite a few projects connecting to the same server (as well as their dev and test stages), and my immediate impression is: if I have only a few projects, it's probably better to use the library. If I have many, there would be diminishing returns as I'd have to scale up each project instance appropriately, which might use more resources overall (compared to one prisma server). Is this correct? Thank you

curious if people are still here since it’s prisma day, but I would like to add a heartbeat endpoint to my graphql-yoga application. This is my code now:

const server = new GraphQLServer({
    typeDefs: './schema.graphql',
    resolvers,
    context: request => ({
        ...request,
    }),
})

server.express.get('/heartbeat', (req, res) => res.send({"up":true}))

server.start({
        port: 8080
    }, () => console.log('Server is running')
)

Why isn’t it picked up?

Happy Prisma Day everyone!

hey guys, is there a guide somewhere about how nexus prisma and prisma2 work in tangent?

moving too fast graphcool, prisma, yoga, graphqlgen, nexus, lift , Photon, prisma2. I hardly manage to get it work before my stuff is legacy.....

If anyone has an idea of what could be wrong with my relay mutation updater preventing QueryRenderer from re-rendering👇🏼 https://github.com/facebook/relay/issues/1701#issuecomment-503569112 🙏

Is it only me or

prisma2 convert

doesn’t work yet?