btw have you built a graphql in front of a preexisting mysql db before? i'm struggling with concept

I have @James - but not with graphcool

I had to use sequelize and manually setup models, etc.

with apollo? do you happen to use PHP inbetween the client and the db? how did you export the schema into graphql, is there a tool? (i have 1000+ columns)

checkout sequelize

ok, let me google about it

its a javascript ORM for SQL databases

@James I think you’re still going to have to manually create model definitions though

hrm, i'm not a fan of running node on public facing stuff

@Ramsay Lanier - You could always rebuild your schema and get your data prepared to be inserted into the datastore. You would want to use Prisma for that.

Hey I have a schema, where I want to replace posts on update

type User {
  name: String,
  posts: [Post!]!
}

I want to replace the posts for the user. But I am not sure how. If I do

mutation {
   updateUser(
      where: {id: "123"},
      data: {
        posts: {
         create: [{title: 'hi}, {title: 'hey'}]
       } 
     }
   )
}

It just appends the posts, instead of replacing them

Cluster API. I send an appProject mutation, it runs ok. Then I send a deploy request. It runs ok, with no errors, but nothing migrates.

{ query: 'mutation($project_name: String!, $stage: String!, $types: String!) {\n    deploy(input: {\n        name: $project_name\n        stage: $stage,\n        types: $types\n    }) {\n        errors {\n            type\n            field\n            description\n        }\n    }\n}',
  variables: 
   { project_name: 'test-project',
     stage: 'local',
     types: 'type Place {... } }

(full types in comment https://github.com/graphcool/prisma/issues/1948#issuecomment-368598581, they are taken from example server) What is wrong?

Quick question: I added a type in database/datamodel.graphql then added it to src/schema.graphql, ran

prisma deploy

and

npm start

, but I cannot perform CRUD operations against the new type. The only queries I see in Schema are the ones under Query in src/schema.graphql. Shouldn't I be able to see the generated ones too?

Would anybody venture a guess as to why a mutation ran through the playground (app default) triggers a subscriptions, but one created through the actual application does not?

Hello everybody! I've got a question that could be considered as noobish. It's about the syntax of a mutation:

list is in this case a relation to another type called List.

I need to associate the ListEntry with a given List, I can identify by its ID.

Could anyone tell me the correct syntax or send me a link, where a this case is explained?

Any help is much appreciated! 🙂

@pasa you don't need to have id in there at all. When you create the mutation, on your resolver you should return the id, task, and list. So your mutation there would look like

just creating a relation should work

what does your data model look like?

But how can I identify the list, when I don't set any id?

Hey I have a schema, where I want to replace posts on update

type User {
name: String,
posts: [Post!]!
}

I want to replace the posts for the user. But I am not sure how. If I do

mutation {
updateUser(
where: {id: "123"},
data: {
posts: {
create: [{title: 'hi}, {title: 'hey'}]
}
}
)
}

It just appends the posts, instead of replacing them

When you create the list, the id will autogenerate

Yeah I get that, but at this moment, the list is already existent and I have its ID stored in my props.