https://www.prisma.io/ logo
Join SlackCommunities
Powered by
# orm-help
  • t
    mine builds a docker container running nginx which pass app engine 8080 traffic through to the node server on 4000, then builds the app and runs it… and app engine rebuilds the entire docker everytime even if i just changed something in JS… annoying, but at least it’s one click and wait and it automatically does the juggling for zero downtime while switching
  • j
    yeah, I probably could have a failed load if someone loaded the site during the 15-30 second filecopy, but I don't have enough traffic to matter 🙂 I could probably implement some kind of very fast swap on s3 if needed.
    👌 1
  • t
    yeah def. mine started out complicated cause I started with https://reactql.org/ sometimes I wish i hadn’t, but overall it was def a plus… going through the SSR setup, it wouldn’t have taken me ages to figure all that out haha
  • j
    yeah SSR is nice
  • t
    Thanks for all the info @tsdexter, been reading and we were wondering if paid tiers were also being affected by this outage. We were going to try to get on paid tier to avoid them since one happened last week while we were trying to demo for one of the first times to a big potential beta client 😬
    👍 1
  • t
    Can someone else chime in and verify who is using prisma if they were affected at all, or is this just a graphcool thing. If it is just a graphcool thing do we need to seriously start considering switching to prisma if we want to avoid these outages?
  • t
    To be clear we've always planned on eventually switching, but we had already committed a lot to getting to production with Graphcool, we figured we could wait it out, but not if this is going to be what happens with graphcool, but not with Prisma
    n
    • 2
    • 2
  • k
    So if there's some kind out outage happening, why isn't it being reflected on status.graph.cool ?
  • k
    I've just spent about 3 hours diagnosing all of my code and reinstalling environments to try and fix whatever's happening, because there's no apparent issue (or even log of an issue) on the status website.
  • k
    I also have a major client demo in 12h. It's past midnight currently. Is there any update or report on what's happening and when it might be fixed?
    n
    • 2
    • 2
  • k
    Is this just free users? Or will this be an issue when we move to production?
  • j
    hello, can someone help? Thank you, much appreciated.
    a
    n
    • 3
    • 43
  • n
    Hey by unistalling graphql cli(like 
    npm uninstall -g graphql-cli
    and 
    yarn global remove graphql-cli
    ) whenever I type graphql it still works in terminal how?
    j
    • 2
    • 17
  • n
    To everyone experiencing issues with Graphcool Cloud right now: We are investigating intermittent issues. Please track https://status.graph.cool/ to stay informed of our progress. We are resolving this as fast as possible. Please reach out to support@graph.cool for any questions 🙂
    🙏 4
    ✅ 1
    • 1
    • 1
  • r
    I needed some guidance with authorising prisma queries. I'll try to explain the use-case we have. This is how part of model we have looks like:
    Copy code
    type User {
	id: ID! @unique
	username: String!
	password: String!
	memberships: [Membership!]!
	...
	...
}

type Blog {
	id: ID! @unique
	name: String!
	isPublished: Boolean @default(value: "false")
	...
	...
}

type Membership {
	id: ID! @unique
	user: User!
	blog: Blog
	...
	...
}
    Now, what I need to do is, whenever query for getting blogs is made, I need to return only those blogs which user has membership of and have been published. Also, I need to respect arguments passed by client in query. Current resolver code without any authorization check looks like
    Copy code
    blogs: async (_, args, ctx: Context, info) => {
    return ctx.prisma.query.blogs(args, info)
}
    One way of achieving this would have been filtering out records returned by Prisma binding call but there is no guarantee that id and isPublished flag would be returned in response.
    n
    • 2
    • 19
  • t
    OS: Windows 10 Pro Node: v8.11.3 Prisma: prisma/1.11.1 (windows-x64) Boilerplate: Advanced @nilan So, I wish to update the feed query to handle pagination and return the record count, which in graphcool framework I do as follows:
    Copy code
    query allPostsCommentsQuery ($first: Int, $skip: Int, $orderBy: PostOrderBy) {
    _allPostsesMeta {
      count
    }
}
    How do I return the count in this prisma instance?
    Copy code
    const FEED_QUERY = gql`
  query FeedQuery($first: Int, $skip: Int, $orderBy: PostOrderByInput) {
    feed(first: $first, skip: $skip, orderBy: $orderBy) {
      id
      text
      title
      isPublished
      author {
        name
      }
    }
  }
`
    n
    • 2
    • 2
  • t
    Copy code
    The relation field `documents` has the wrong format: `[File]` Possible Formats: `File`, `File!`, `[File!]!`
  • t
    I don't get it. How can I specify nullable array?
    v
    n
    • 3
    • 15
  • s
    Hi, i still have the message 
    We're currently synchronizing your project data. Please wait a little bit until Billing is available here.
    I contacted the support team but after days I still have no response, fact that leads me to the second question: the shared cluster project account, which I will use with graphcool-framework, has the email support, but how long is the support is going to take to get in touch? If i have a time sensitive/ critical question can i expect a response in 1/10/24/48... hours?
  • k
    What’s everybody using for heir API documentation? We’re looking for something interactive but not Graphiql
    t
    • 2
    • 2
  • j
    I have a question about the @pgRelation directive. Can anyone help me ?
  • t
    Copy code
    You are creating a required field but there are already nodes present that would violate that constraint
    I know that this is an "expected behaviour" that adding required fields with default doesn't work, but how this can be worked around?
    h
    w
    n
    • 4
    • 11
  • h
    Does prisma support caching and batching?
  • k
    @nilan I'm still experiencing errors with graph.cool
    n
    • 2
    • 1
  • k
    Please help! my client meeting is in less than an hour.
    t
    • 2
    • 1
  • k
    Status page still says ✅
  • k
  • t
    My prisma docker container just keeps restarting
  • t
    @nilan is it a bad image? It appears to be using 
    prismagraphql/prisma:1.11
  • t
    Seems to be the latest in docs
1...808182...637Latest