We have users who are one to many on user settings and the id of every user using a setting is stored on the setting in any array

It could be a visual thing instead of a data thing though

Is there a video of @sorenbs talk from the Europe conference? https://graphql-europe.org/schedule/schema-first-development

@joshmadewell I found this googling

A one-to-many relationship is a relationship where a parent record can be linked to many children. For example, a user can be an author of many stories. In our SQL database it means the Story table will have an author column, storing an id of a User as a foreign key. The User table will not need to store any references to stories in the SQL schema.

However in the GraphQL schema, Story will have an author field of type User and User will have stories. This allows queries to follow relationships (connections) from both sides, regardless of the underlying SQL schema. The way the data is stored and represented in the database is an implementation detail.

if thats the same in graph.cool, that’s ok I guess. but I wonder if there’s a char limit for the field

Car.wheels

that I may hit in my example

ahh that makes total sense

but still a valid concern about the size of that data

yeah it’d be good if we can get an estimate on size limit. Update: Looks like its around

280,403 chars

so if new id adds 29 chars

"id",

that’ll give around 9.6k records. If I did a player (one) to statEvent (many) relationship. Russell Westbrook would hit the size limit in 2seasons as I estimate he did 8.5k statEvents this season (e.g. Points, Assist, Steals, Blocks)

hey all — sooo… I have a design question wrt graphcool and stripe integration — would this be the spot to ask it?

😦 when trying to create a subscription

guess nobody is there

Whoops. Looks like an internal server error. Please contact us in Slack (https://slack.graph.cool) and send us your Request ID: cj4qrekrf1k5v019618n9p0jg

can any help me out ...! i am getting this issue when i toggle off a function

and my changes are not been saved ...!

I am trying to make a user profile page for my app with react native. The UserType contains {email, username, password, age}. {age} is an [optional] field. When I try to query a User that doesn’t have {age} field... I get an error saying “age not defined”. I am planning to have more {...fields} later on. How can I battle this issue? I was thinking of making if (!age) { ... } but then I will need to do that for all of the optional fields?

This message was deleted.

I reposted my issue on the discussion boards, as requested. 🙂 https://www.graph.cool/forum/t/confusing-error-message-on-one-to-many-update/308

okay, so my stripe integration question goes a little like this

I want to retrieve the saved cards for a particular customer on Stripe. In order to do this, I have to use a back-end server, but would prefer to do it through graphql. Would you use post-processing SSR to handle fetching a stripe customer?

or should I be barking up a different tree?

Q: I read somewhere that doing a count automatically groups on the result of the result fields. Is that correct, or did I misinterpret something?

Can I create deeply nested mutations?

More than just one to many?

Author -> posts -> tags?

reading through this https://www.graph.cool/docs/reference/simple-api/nested-create-mutations-vaet3eengo/

are we using propTypes when using Apollo?

I just tried and got some errors but found this:

`const doc = gql`query { ... }`; X.propTypes = { data: propType(doc).isRequired, };`

on https://github.com/apollographql/graphql-anywhere

Wondering if I could receive some crowdsourced assistance for a

query

. How would one query

Connections

for current

user

where either

user

has not blocked the

connection

or vice versa? Here’s the simplified schema:

type User implements Node {
  id: ID! @isUnique
  blockTarget: [Blocks!]! @relation(name: "BlockTargetToUser")
  blockSource: [Blocks!]! @relation(name: "BlockSourceToUser")
}
type Connections implements Node {
  id: ID! @isUnique
  source: User @relation(name: "ConnectionSourceToUser")
  target: User @relation(name: "ConnectionTargetToUser")
}
type Blocks implements Node {
  id: ID! @isUnique
  source: User @relation(name: "BlockSourceToUser")
  target: User @relation(name: "BlockTargetToUser")
}

Currently, the

query

for finding connections for each user doesn’t consider which user blocked whom:

{
  allConnectionses(filter: {
    OR: [
      { source: { id: userId } },
      { target: { id: userId } }
    ]
  }) {
    id
    source {
      id
    }
    target {
      id
    }
  }
}