I don't understand why I should use graphql-nexus and nexus-prisma over a simple schema.graphql and resolvers with graphql-yoga

If I do simple typescript will provide me completion with because I use directly prisma-client

But if I do it with nexus the context from the resolve has prisma and I can use prisma but typescript won't offer me any completion

I just want to understand what's up with these

hi, everybody. Is there a channel for begginers' questions? Trying do deploy prisma server on Windows 8.1 (with Docker) to create a React app following the tutorial at https://www.prisma.io/tutorials/build-react-graphql-app-with-fetch-ct19

1. Installed Docker 2. I run the docker-compose; MySQL and PrismaGraphQL are up. The logs of both Docker containers have nothing strange. - last lines of logs from MySQL:

2019-03-25T23:53:45.323196Z 0 [Note] mysqld: ready for connections.
Version: '5.7.25'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)`

- from Prisma GraphQL:

Successfully started 1 workers.
Server running on :4466
Version is up to date.

When I run

prisma deploy

the error message

Could not connect to server at <http://prisma:4466>. Please check if your server is running

is returned. I tried to change

prisma

to

localhost

and the message is the same.

If I change the hostname to

host.docker.internal

then the error message is

Creating stage default for service default... !
 !    'ENOTFOUND': request to <http://host.docker.internal:4466/management>
 !    failed, reason: getaddrinfo ENOTFOUND host.docker.internal
 !    host.docker.internal:4466

Hi, im traying to deploy to AWS but i have a problem with the prisma cloud service. Can someone help me?

Is there anything special about errors in prisma-client? I couldn't find any mention of validation in the docs. When I want to fail validation shall I just

throw new Error("message")

or are there any special error codes or error objects I should be using?

Hello guys! In the attached image I have a set of available operations for an image field. I want to use set and create at the same time but it seems that set is always executed after create, no matter if the order is create and set or vice versa. Can I do something to execute set before create? Thanks in advance.

I have never been able to get

orderBy

to work with

'createdAt_ASC'

or

'createdAt_DESC'

. Am i missing something? I can query

createdAt

in the front end and display it in the UI but can't seem to sort data by it

For example, I'm just trying to order a users feed by creation date of posts:

feed: async (_, { id }, ctx, info) => {
    const following = await ctx.prisma.user({ id }, info).following();
    const followingIds = following.map(follower => follower.id);

    return ctx.prisma.posts(
      {
        where: {
          author: { id_in: [...followingIds, ctx.request.userId] }
        },
        orderBy: "createdAt_ASC",
      },
      info
    );
  },

There is a bug in

prisma@beta

when I mark my custom field with

@createdAt

tag it doesn’t generate

prisma-client

like it’s supposed to

Basically the field is generated with

DateTimeInput

instead of

DateTimeOutput

Hi

Hi 👋 Question about scaling Prisma and HA. simple smile Is it possible to have multiple prisma servers running on the same database, say for instance I have 10-20 services all connected to a pool of 3 prisma servers running behind a loadbalancer. Is this possible? And also, how is the realtime mechanism built into prisma, does it intgrate over the database, say one application creates something which two other applications subscribes to, but this happens on another prisme server. Does all the subscribers get this event? I see the server takes in some rabbitMQ url[1], is this needed to get this working? Did not find that much documentation on this 😅 [1] https://github.com/prisma/prisma/blob/0abb28a6f92e6999139055e5259ab7f7cff23429/server/libs/prisma-config/src/main/scala/com/prisma/config/ConfigLoader.scala#L361

Hello, I'm having this message when I run docker-compose up after I init my prisma

prisma_1  | Exception in thread "main" org.postgresql.util.PSQLException: ERROR: Unsupported startup parameter: search_path
prisma_1  |     at org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:473)
prisma_1  |     at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:205)
prisma_1  |     at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:49)
prisma_1  |     at org.postgresql.jdbc.PgConnection.<init>(PgConnection.java:195)
prisma_1  |     at org.postgresql.Driver.makeConnection(Driver.java:452)
prisma_1  |     at org.postgresql.Driver.connect(Driver.java:254)
prisma_1  |     at slick.jdbc.DriverDataSource.getConnection(DriverDataSource.scala:101)
prisma_1  |     at slick.jdbc.DataSourceJdbcDataSource.createConnection(JdbcDataSource.scala:68)
prisma_1  |     at slick.jdbc.JdbcBackend$BaseSession.<init>(JdbcBackend.scala:453)
prisma_1  |     at slick.jdbc.JdbcBackend$DatabaseDef.createSession(JdbcBackend.scala:46)
prisma_1  |     at slick.jdbc.JdbcBackend$DatabaseDef.createSession(JdbcBackend.scala:37)
prisma_1  |     at slick.basic.BasicBackend$DatabaseDef.acquireSession(BasicBackend.scala:249)
prisma_1  |     at slick.basic.BasicBackend$DatabaseDef.acquireSession$(BasicBackend.scala:248)
prisma_1  |     at slick.jdbc.JdbcBackend$DatabaseDef.acquireSession(JdbcBackend.scala:37)
prisma_1  |     at slick.basic.BasicBackend$DatabaseDef$$anon$2.run(BasicBackend.scala:274)
prisma_1  |     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
prisma_1  |     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
prisma_1  |     at java.lang.Thread.run(Thread.java:748)

I've searched online and found nothing about prisma

Having an issue updating an enum within Prisma Admin. Gives me an add item, but clicking on the item within the list does not actually add the item

Nevermind, fixed the above by re-running the query and adding the enum into the actual query.

I’d like to store the

PRISMA_CONFIG

as a kubernetes secret. I am aware it has some piping formating, does anyone have an example of how that is stored?

I am getting unknown Host exception while connecting to an existing local database

In the docker-compose.yml, the host shown is host.docker.internal

prisma init missing fullstack template

Hi all. I’ve been running into a problem with tokens and Prisma recently and I’m not sure what’s happening…. I’ve set up my prisma.yml to have a secret but my token seems to reset or expire every time I save the project! This means that I need to paste a new endpoint URL into my .env almost every time I change anything. Is this a known issue? Am I doing something dumb?