- u
user
01/19/2018, 1:34 PM@sdubois commented on @fabien0102’s file: that sounds great, you should post it in the github issue 👍https://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- u
user
01/19/2018, 1:37 PM@fabien0102 commented on @fabien0102’s file: Done!https://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- t
telmo
01/19/2018, 1:45 PManyone managed to deploy
to now ?prismaijn- 4
- 11
- u
user
01/19/2018, 2:35 PM@iamclaytonray commented on @fabien0102’s file: Figured I’d mention, I’m trying to get a Version scalar type baked into core.https://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- u
user
01/19/2018, 2:36 PM@iamclaytonray commented on @fabien0102’s file: https://github.com/graphcool/prisma/issues/1369https://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- u
user
01/19/2018, 2:36 PM@iamclaytonray commented on @fabien0102’s file: I’d love some feedbackhttps://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- h
harmony
01/19/2018, 2:37 PMwhy do all image comments get published to the channel 🤔fast parrot 1id- 3
- 5
- u
user
01/19/2018, 2:38 PM@fabien0102 commented on @fabien0102’s file: I personnally prefer my POC version, just because I don't need to filter on thehttps://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
to have my products (so my API don't change, I only add anversion
field)history - u
user
01/19/2018, 2:40 PM@fabien0102 commented on @fabien0102’s file: BTW, if you want this kind of field, you can easily add a hook to process thehttps://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
on each update (as me)version - u
user
01/19/2018, 2:40 PM@iamclaytonray commented on @fabien0102’s file: So you’ll never query for a previous record of a product?https://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- u
user
01/19/2018, 2:41 PM@fabien0102 commented on @fabien0102’s file: I will, but only if I want the historyhttps://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- u
user
01/19/2018, 2:41 PM@fabien0102 commented on @fabien0102’s file: It's just a field (or a collection)https://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- u
user
01/19/2018, 2:41 PM@fabien0102 commented on @fabien0102’s file: But I don't want to add a filter to each queries if I only need the last versionhttps://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- u
user
01/19/2018, 2:42 PM@fabien0102 commented on @fabien0102’s file: (the versionning is just for the administrative part)https://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- u
user
01/19/2018, 2:42 PM@iamclaytonray commented on @fabien0102’s file: Another use-case is to query only a past version. For example, say I rewrite Github. Being able to go back in time to a previous commit is crucial functionalityhttps://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- u
user
01/19/2018, 2:42 PM@iamclaytonray commented on @fabien0102’s file: By default, it query’s the latest recordhttps://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- u
user
01/19/2018, 2:44 PM@fabien0102 commented on @fabien0102’s file: I can query on PostHistory easilyhttps://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- u
user
01/19/2018, 2:44 PM@fabien0102 commented on @fabien0102’s file: 😉https://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- u
user
01/19/2018, 2:44 PM@iamclaytonray commented on @fabien0102’s file: You’re missing the point and the use case, hahahttps://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- u
user
01/19/2018, 2:44 PM@fabien0102 commented on @fabien0102’s file: Maybe ^^https://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- u
user
01/19/2018, 2:44 PM@iamclaytonray commented on @fabien0102’s file: That becomes a heavy burden to managehttps://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- u
user
01/19/2018, 2:45 PM@iamclaytonray commented on @fabien0102’s file: It make sense to use a single scalarhttps://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- u
user
01/19/2018, 2:45 PM@fabien0102 commented on @fabien0102’s file: For goback I will just update the modelhttps://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- u
user
01/19/2018, 2:45 PM@fabien0102 commented on @fabien0102’s file: (as a merge commit)https://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- u
user
01/19/2018, 2:45 PM@fabien0102 commented on @fabien0102’s file: 😉https://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- u
user
01/19/2018, 2:47 PM@iamclaytonray commented on @fabien0102’s file: Then it becomes, do you version the entire record every time? Only portions of the record? Validation? What database? Do you need to write this over and over for each database? You’re looking at your use case. I’m looking at the general population and implementing something agnostic to any one use casehttps://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- u
user
01/19/2018, 2:47 PM@fabien0102 commented on @fabien0102’s file: For a fist version, the entire record, to have an easier managementhttps://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- u
user
01/19/2018, 2:47 PM@fabien0102 commented on @fabien0102’s file: But yes, I will prefer just a diffhttps://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- u
user
01/19/2018, 2:48 PM@iamclaytonray commented on @fabien0102’s file: Haha, okay man 👍https://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾
- u
user
01/19/2018, 2:49 PM@fabien0102 commented on @fabien0102’s file: Not perfect, but it should make the job ^^https://prisma.slack.com/files/U7AUJD4SV/F8WF5F555/image.png▾