this gave me a link to my hosted prisma server

On my frontend, I have Apollo Client. Do I replace the Apollo Client uri with this heroku address?

or do I keep it as http://localhost:4000

no you should use the heroku endpoint in your apollo server config and keep http://localhost:4000 on the frontend

ok, that's what I thought. Even though it works either way which I don't understand. In the Wes Bos advanced react tutorial, he replaces the uri with the heroku link when deploying

something like this :

const db = new Prisma({
  typeDefs: "src/generated/prisma.graphql", // the auto-generated GraphQL schema of the Prisma API
  endpoint: "<https://url.to.endpoint>", // the endpoint of the Prisma API (value set in `.env`)
  debug: true // log all GraphQL queries & mutations sent to the Prisma API
  // secret: process.env.PRISMA_SECRET, // only needed if specified in `database/prisma.yml` (value set in `.env`)
});

const params = {
  typeDefs: importSchema(path.resolve("./src/schema.graphql")), // Your custom schema
  resolvers, // Your resolvers
  introspection: true, // automatic in DEV but needed in PROD too
  //playground: true, automatic in DEV
  context: req => ({
    ...req,
    db
  })
};

const server = new ApolloServer(params);

yeah thats the backend

my apollo client looks like

function createClient(initialState) {
  return new ApolloClient({
    connectToDevTools: process.browser,
    ssrMode: !process.browser, // Disables forceFetch on the server (so queries are only run once)
    link: new HttpLink({
      uri: process.env.NODE_ENV === 'development' ? DEV_ENDPOINT : PROD_ENDPOINT,

DEV_ENDPOINT

is my localhost,

PROD_ENDPOINT

is the heroku link

thats how Wes Bos set it up

can’t tell, but the idea is that you have a prisma instance, an apollo server calling the prisma api, and the frontend is supposed to call the apollo server

Looking for the magic sauce to getting pyton websockets to subscribe to prisma subscriptions. I have tried everything, but I cannot get the socket to return anything other than 200.

have you tried javascript?

@Chase There are 2 different heroku urls, one is the prisma api, the other is the apollo server deployed to heroku

this one is apollo server running on heroku

while this one is the prisma api endpoint : https://github.com/wesbos/Advanced-React/blob/master/finished-application/backend/prisma.yml#L2

oh my, im going dyslexic. thank you very much for catching that

since my frontend and backend are on the same host, explains why localhost works in production

How does one access JVM logs of a prisma server? (It's running under Docker in a vm) I was able to get at the docker logs. I suspect the JVM flopped over and want to check the logs.

So, I'm continually receiving the spinning wheel of death when attempting to view the services data-browser for my project on Eu1. Are there any known issues with the service?

hey does Prisma currently support JSONB for postgres?

Hi, a question about queries in Prisma: A User can have many Posts. How would we show a list of users and their total number of Posts?

users { id posts { id } }

and then counting

user.posts.length

in the frontend would work, but we cannot sort users by post amount from DB if we have pagination, right? I think requesting

users { id postsConnections { aggregate { count } } }

or similar is not supported by Prisma (in one single request), and if it was probably we cannot order by that in the same request. Another solution would be adding a

totalPosts

counter to the user and increment it every time a user writes a post, but atomic increments are not supported either so there could be issues with this as well. Therefore, what’s the recommended way to do this?

Any ETA for the datamodel v1.1?

@Harshit @marcus I get this error when trying to delete an `event`:

The change you are trying to make would violate the required relation 'EventToParticipant' between Event and Participant

...

I've read about this here: https://github.com/prisma/prisma/issues/1262

do I have to add

onDelete: CASCADE

to the schema?

You have to remove the "offending" nodes or reset the instance if you are just testing

You probably are adding a required rule to a field but there are rows with null in this field