drk
05/30/2018, 3:34 AMJeff
05/30/2018, 3:37 AMuser
05/30/2018, 5:22 AMsnolahc
05/30/2018, 6:42 AMChristian
05/30/2018, 7:05 AMArnab
05/30/2018, 7:22 AMWorks across any kind of
database
headline followed by Currently supports Postgres and MySQL
š
siyfion
05/30/2018, 8:33 AMsiyfion
05/30/2018, 9:41 AM$ prisma seed --reset
Seeding based on node seed.js !
āø cross_spawn_1.default is not a function
Get in touch if you need help: <https://www.graph.cool/forum>
To get more detailed output, run $ export DEBUG="*"
siyfion
05/30/2018, 9:41 AMnode seed.js
myself it works fine�fredelf
05/30/2018, 1:02 PMsiyfion
05/30/2018, 1:07 PMJscott388
05/30/2018, 2:51 PMhez
05/30/2018, 4:32 PMMichael Jones
05/30/2018, 4:52 PMmarano
05/30/2018, 5:40 PMpeter
05/30/2018, 6:49 PMprisma ls
show all my deployed services? I have one service currently deployed but executing prisma ls
returns 'No deployed service found'. Additionally, when running prisma info
(in prisma dir), the cli returns the http and ws endpoints as expected...this seems like a problem, no?codebeast
05/30/2018, 6:53 PMpicosam
05/30/2018, 7:44 PMquery {
id
multilingualData {
language
title
}
}
where info would be an array. I want the user to query GraphQL Yoga as follows:
query {
id
title
}
It is, of course, easy to map the Prisma result to another object and return it to the user. But then the info
argument comes into play. In order for me to fetch multilingualData
I have to pass an info
object to the Prisma query, the following string for example: { id multilingualData { language title } }
which is of course error-prone. Any thoughts on how to better achieve this?picosam
05/30/2018, 7:57 PMwillvincent
05/30/2018, 7:58 PMwillvincent
05/30/2018, 7:58 PMsplodingsocks
05/30/2018, 8:52 PMsplodingsocks
05/30/2018, 8:52 PMsplodingsocks
05/30/2018, 8:52 PMsplodingsocks
05/30/2018, 8:55 PMsplodingsocks
05/30/2018, 8:55 PMmatic
05/30/2018, 8:56 PMKien Vo
05/30/2018, 8:59 PMwillvincent
05/30/2018, 9:10 PMid: !ID @unique
name: String!
geodata: String!
and geodata will store stringified json, and then when querying I want the resolver to manipulate that json data somehow, for sake of argument lets say manipulate it into valid geojson, but for reasons Iām not going to go into I donāt need or want an actual geojson field in the database for this data attribute.
How might one go about manipulating data in a resolver and similarly in a mutation, as itās going into/coming out of the data store?willvincent
05/30/2018, 9:10 PM