Hi guys, I was playing around with graphcool on local server and noticed that it created different db tables when adding a relation. What I wanted was to have a normalized schema where i can store ids of two related models as a foreign key. The reason for that is this db may be transferrred to a person who will do analytics on it later and I want db to be in a condition where another person can understand it and use it with his own tools. right now the relations tables have an id-name which does not say anything unless you look inside it is there a way to keep db normalized and still use graphql? What other options can i explore?

We just released

prisma@1.2.0

with a bunch of improvements and cascading deletes support: https://github.com/graphcool/prisma/releases/tag/1.2.0 Let me know how you like it! 🙂

trying to deploy to the prisma-eu1 cluster, I got this error (I'm using prisma v1.2):

ERROR: Cannot query field 'description' on type 'Cluster'. (line 8, column 5):
    description
    ^

{
  "data": {
    "generateClusterToken": null
  },
  "errors": [
    {
      "message": "Cannot query field 'description' on type 'Cluster'. (line 8, column 5):\n    description\n   ^",
      "locations": [],
      "path": []
    }
  ],
  "status": 200
}

@andre pinned a message to this channel.

Hi there, just started with some backend stuff and playing around with Prisma. I’m setting up a file server, have a file watcher watching for logs/files and create an entry/node when needed. Now this seems to work fine, except when the new file is supposed to replace an existing entry. Note, these mutations are called server side.

Now in playground if I query the database I get back the latest added and updated nodes, if I query the app I only get back the entries that existed when the server was started. Why doesn’t it work or am I wrong in my expectations on how Prisma works?

upgraded to 1.2 and now I get this:

Error: Cannot use GraphQLNonNull "[CartItem]!" from another module or realm.

Ensure that there is only one instance of "graphql" in the node_modules
directory. If different versions of "graphql" are the dependencies of other
relied on modules, use "resolutions" to ensure only one version is installed.

<https://yarnpkg.com/en/docs/selective-version-resolutions>

Duplicate "graphql" modules cannot be used at the same time since different
versions may have different capabilities and behavior. The data from one
version used in the function from another could produce confusing and
spurious results.

Does npm have something similar to this?

I am not sure who cares but the https://www.graphql-europe.org/ website has an exception at the bottom of the page in IE - uh oh!

@Ben commented on @Discere’s file : Just being curious: did you deliberately test it in IE or is this your standard browser?

It is standard for our firm

The error message should have said: "Something unexpected happened. Someone used IE" 😄

So does Prisma take away the need to write connectors?

and something like sequelize?

is it possible to specify what gets returned from an update or create command? Like we do with queries. I’m trying to return the newly created item, but also a nested item http://wes.io/pW4d

DOH

thats how it works, I just need to update my client side query to ask for this data

New question - where do I find docs for the arguments that the resolver passes us?

async addToCart(parent, args, ctx, info) {

@nilan when you guys say that Prisma will be merged back into the Graphcool framework does that mean that graphql-yoga and prisma will be running on the same server?

Anyone seeing connectivity issues today with graph.cool simple api? We’re getting sporadic 504s

yeah

Yes, I am seeing slowness and dropped connections too

I am. About to do a client demo so just loading everything into the apollo client cache before the meeting by clicking on every link 🙄 it'll look blazing fast

@max: clever

it was until my app just crashed on something undefined 😥

looks like graphcool is back running at full speed 🙂 only a short slow down. Someone must have been stressing the service

are there any examples demonstrating a system with

prisma

+

apollo-engine

?

Is there a way to upsert

connect

in a mutation other than manually asking if the node exists? I don't know if the node exists, so I'm not sure if I need to

connect

or

create

It looks like no and

upsert

may be dead as a nested method. https://github.com/graphcool/prisma/issues/1280