https://www.prisma.io/ logo
Join SlackCommunities
Powered by
# orm-help
  • s

    Steven Vachon

    06/03/2019, 4:15 PM
    Copy code
    type Thing {
      id: ID! @id
      value: String
    }
    Copy code
    curl -X POST -H "Content-Type: application/json" --data '{ "query": "{ thing { value } }" }' <http://localhost:4466>
    Field 'thing' argument 'where' of type 'ThingWhereUniqueInput!' is required but not provided.
    d
    j
    e
    • 4
    • 33
  • k

    koia

    06/03/2019, 5:54 PM
    hello everybody prisma cool
  • k

    koia

    06/03/2019, 5:58 PM
    I'm new to Prisma, I was wondering how does Prisma maintains relationships between entities in the DB, since I don't see any join table. For example between User and Message there is not UserMessage table but I see in my queries a messages properties and can query all the messages
    m
    • 2
    • 2
  • k

    koia

    06/03/2019, 5:58 PM
    sorry for such a long question🐧
  • k

    koia

    06/03/2019, 6:01 PM
    I'm using Postgres and Prisma 1.34.0 by the way
  • t

    Travis

    06/03/2019, 6:58 PM
    Do you need to use Docker with Prisma? I'd like to first learn/use Prisma for all local development, then leverage Docker, once I'm ready for that stage.
    m
    • 2
    • 1
  • s

    schrepfler

    06/04/2019, 12:28 AM
    what exactly has been re-written in rust, the server part?
    d
    • 2
    • 1
  • t

    tanuj doshi

    06/04/2019, 10:26 AM
    ! 'ECONNREFUSED': request to http://192.168.99.100:4466/management failed, reason: connect ECONNREFUSED 192.168.99.100:4466
  • t

    tanuj doshi

    06/04/2019, 10:26 AM
    anyone plz?
  • t

    tanuj doshi

    06/04/2019, 10:26 AM
    in prisma deploy
  • t

    tanuj doshi

    06/04/2019, 10:29 AM
    ```
  • t

    tanuj doshi

    06/04/2019, 10:29 AM
    Copy code
    PS C:\Users\DHRUMIT\Desktop\mysql-node\helloworld> prisma deploy
    Creating stage aada for service aada √
    Deploying service `aada` to stage `aada` to server `default` !
     !    'ECONNREFUSED': request to <http://192.168.99.100:4466/management> failed, reason: connect ECONNREFUSED 192.168.99.100:4466
    
    Get in touch if you need help: <https://www.prisma.io/forum/>
    To get more detailed output, run $ export DEBUG="*"
  • t

    tanuj doshi

    06/04/2019, 10:33 AM
    answers are appreciated , please
    d
    a
    • 3
    • 2
  • a

    Andre Coetzee

    06/04/2019, 11:35 AM
    show your latest docker log. Your answer should be in there
  • a

    Andre Coetzee

    06/04/2019, 11:37 AM
    docker-compose logs -t -f --tail=200
  • c

    Clément Fassot

    06/04/2019, 12:00 PM
    Hey guys, I have a question for you. My team and I want to create a "back-end as a service" service for our internal applications, then stitch all schemas in a gateway that would authenticate users using a jwt (auth0 in this case). Schemas would have directives to describe permissions (something like
    @query('HR Management') @mutation('Management')
    ). A developer would then just need to produce a datamodel for prisma with the right directives. At first we thought about doing a gateway that stitches a list of schemas automatically, but with recent announces of Apollo federation/gateway and the fact that prisma will soon no longer need a prisma server to do its magic we're forced to reassess things. I think we could deploy an apollo federation service for each "backend" we provide, this service uses the datamodel of prisma as its graphql schema. Problem is we need to generate the resolvers, or have the developer write them (would be very easy but quite long sometimes). Or we could do a CLI that generates them using the datamodel and prisma client. What do you guys think ? Have anyone of you been in this situation before where you want to generate resolvers automatically based on a datamodel ?
    a
    • 2
    • 1
  • y

    yolen

    06/04/2019, 12:09 PM
    MAYDAY MAYDAY ssl certificates expired on graphcool backend. Please help @schickling @Harshit
  • l

    lkbr

    06/04/2019, 12:10 PM
    Out site is down too: "[Network error]: FetchError: request to https://api.graph.cool/simple/v1/xxx failed, reason: certificate has expired"
  • d

    dpetrick

    06/04/2019, 12:11 PM
    We're on it.
    🚼 3
    y
    • 2
    • 2
  • m

    Michał Chmura

    06/04/2019, 12:13 PM
    ping 👇
    n
    • 2
    • 4
  • k

    Kimble

    06/04/2019, 12:29 PM
    I know you're on it but nothing like another complaint to get things moving!!
  • j

    joar

    06/04/2019, 12:36 PM
    Are prisma users affected by this too? Or only graphcool?
    d
    • 2
    • 1
  • k

    Kimble

    06/04/2019, 12:50 PM
    Hey - FYI it seems to be back for me
    👍 1
    🦜 1
  • k

    Kimble

    06/04/2019, 12:52 PM
    make sure to set a calendar reminder for next year...graphcool is still great you guys should get back on it - still the best "serverless" solution out there even if its been neglected for a while
  • k

    Kimble

    06/04/2019, 12:54 PM
    still propagating it seems so not everyone may have their party hats on yet
  • r

    rpeterson

    06/04/2019, 1:22 PM
    @schickling or team - Congrats on the 2.0 announcement, sounds awesome! As always, I am starting a new contract building out a MVP for a contract starting this week and we were looking at Prisma to be part of the stack. What are the risks with going early-in on Prisma 2.0 that you may know of or could see possibly being a reason to just implement in 1.0 and migrate later this year?
    j
    m
    +2
    • 5
    • 4
  • c

    Csaba Tamas

    06/04/2019, 1:34 PM
    hi guys, greetings from AWS, let me know if you’re looking for guidance for your topics
    j
    • 2
    • 4
  • h

    Hoang

    06/04/2019, 1:57 PM
    Hi guys, any ideas on how to fix this please?
    Copy code
    (node:5226) UnhandledPromiseRejectionWarning: Error: Project not found: 'default$default'
        at BatchedGraphQLClient.<anonymous> (/Users/pham/dev/adviqo/calling-service/node_modules/http-link-dataloader/dist/src/BatchedGraphQLClient.js:69:35)
        at step (/Users/pham/dev/adviqo/calling-service/node_modules/http-link-dataloader/dist/src/BatchedGraphQLClient.js:40:23)
        at Object.next (/Users/pham/dev/adviqo/calling-service/node_modules/http-link-dataloader/dist/src/BatchedGraphQLClient.js:21:53)
        at fulfilled (/Users/pham/dev/adviqo/calling-service/node_modules/http-link-dataloader/dist/src/BatchedGraphQLClient.js:12:58)
        at <anonymous>
        at process._tickCallback (internal/process/next_tick.js:189:7)
    (node:5226) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
    (node:5226) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
  • h

    Hoang

    06/04/2019, 2:02 PM
    Copy code
    ERROR: Whoops. Looks like an internal server error. Search your server logs for request ID: local:cjwhvghbr000b0849nt6jvtno
    
    {
      "data": {
        "addProject": null
      },
      "errors": [
        {
          "message": "Whoops. Looks like an internal server error. Search your server logs for request ID: local:cjwhvghbr000b0849nt6jvtno",
          "path": [
            "addProject"
          ],
          "locations": [
            {
              "line": 2,
              "column": 9
            }
          ],
          "requestId": "local:cjwhvghbr000b0849nt6jvtno"
        }
      ],
      "status": 200
    }
    h
    a
    • 3
    • 5
  • s

    Stephen Jensen

    06/04/2019, 2:14 PM
    Could anyone explain to me how Prisma 2 will use Rust even though it can be run as a NPM or Golang package? I didn’t realize that NPM is capable of running Rust binaries directly and I’m wondering what the architecture would be if it was running in a lambda function.
    c
    j
    +2
    • 5
    • 10
1...275276277...637Latest