Thomas
04/09/2019, 5:31 AMrdc
04/09/2019, 5:44 AMdocker-compose.yml
-> It is inside on the same folder! Would docker-compose up -d
put it inside the image?Stanislav
04/09/2019, 6:35 AMAl
04/09/2019, 7:30 AMboyney123
04/09/2019, 7:45 AMAndrei Bacescu
04/09/2019, 8:17 AMsoosap
04/09/2019, 10:23 AMnuno
04/09/2019, 11:21 AMJames
04/09/2019, 11:57 AMs1nc4p
04/09/2019, 1:34 PMhumblefool
04/09/2019, 2:15 PMschema.graphql
files (there can be more once the entities increase) with their separate types and queries and mutations. I am using extend
keyword to extend mutations and queries in those. But, when I am trying to run the server, it does not seem to have find the query and mutations defined in one schema file. I am creating the server like this new GraphQLServer({
typeDefs: [ '111.schema.graphql',
'222.schema.graphql',
],
resolvers,
context: { prisma },
});
If this is not the right place, could you please point me to the correct place, if you happen to know one.ervindraganovic
04/09/2019, 2:42 PMalli
04/09/2019, 5:47 PMz01
04/09/2019, 7:28 PM@indexes
directive live with the current data model 1.1 preview? I am trying to create a composite index, but while I am getting no error during prisma deploy
phase, the index is not being created.csamu
04/10/2019, 9:28 AMMJ
04/10/2019, 9:47 AMFran Dios
04/10/2019, 10:18 AMNick
04/10/2019, 10:30 AMNick
04/10/2019, 10:32 AMNick
04/10/2019, 10:35 AMrem
04/10/2019, 11:51 AMgraphql-request
and before all tests run, I start a local (to the process) server that I can query and check expected results and mutations https://cloudup.com/cBDLDedjeqUrem
04/10/2019, 11:53 AMNick
04/10/2019, 12:23 PMNick
04/10/2019, 4:00 PMpancake
04/10/2019, 5:18 PM@rename
directive doesn’t appear to work as I assume it does, perhaps one of you could quickly point me right.
I have a data model
type Organization {
...
defaultPlanner: OrgUser! @relation(name: "DefaultPlanner") @unique
}
which I wish to change to
type Organization {
...
defaultOrgUser: OrgUser! @relation(name: "DefaultOrgUser") @unique
}
however, when I modify it as
defaultOrgUser: OrgUser! @relation(name: "DefaultOrgUser") @unique @rename(oldName: "defaultPlanner")
I lose all the data in the field, which seems contrary to how the @rename directive is supposed to work.
What am I missing?Naka
04/10/2019, 10:52 PM1.20.5
and want to use set
feature between relations that was added later. Is there an update guide with breaking changes? I found Update to ...
links on Release and Maintenance section on prisma docs but they are outdated.ahebwa49
04/11/2019, 6:49 AMahebwa49
04/11/2019, 6:50 AMahebwa49
04/11/2019, 6:51 AMahebwa49
04/11/2019, 6:51 AMtype Query {
users: [User]!
items(
where: ItemWhereInput
orderBy: ItemOrderByInput
skip: Int
first: Int
): [Item!]!
item(id: ID!): Item
profile: User
itemsConnection(where: ItemWhereInput): ItemConnection!
cart(where: CartItemWhereUniqueInput!): CartItem!
order(id: ID!): Order
}