# orm-help
- c
CCBCodeMonkey
02/21/2019, 7:36 PM - d
dan
02/21/2019, 7:36 PMAll our deployments are automated with circle and clusters - c
CCBCodeMonkey
02/21/2019, 7:36 PMyea for me I just do a checkin with the first schema, and a checkin with the next schema - c
CCBCodeMonkey
02/21/2019, 7:37 PMit is something they should fix - d
dan
02/21/2019, 7:37 PMLike any other framework, the default value would be set when adding the field 🙄 - c
CCBCodeMonkey
02/21/2019, 7:37 PMI do validations on top of prisma anyways when I save data - c
CCBCodeMonkey
02/21/2019, 7:37 PMso the whole required field isn't a huge deal for me - c
CCBCodeMonkey
02/21/2019, 7:37 PMthey could use a whole lot more stuff around validations - d
dan
02/21/2019, 7:38 PMThe reason you make it required is for the generated graphql schema and client - d
dan
02/21/2019, 7:39 PMUgh, this is not just a bug, its a flaw - d
dan
02/21/2019, 7:40 PMIf a field is required, it should also require a default value, problem solved. - c
CCBCodeMonkey
02/21/2019, 7:44 PMno? I could see having a required field without a default value - c
CCBCodeMonkey
02/21/2019, 7:44 PMthat would mean whatever is inserting the data would have to make sure that field is there or it fails to insert - c
CCBCodeMonkey
02/21/2019, 7:45 PMyou are saying, adding required to data with existing rows would require a default value, then yes I agree with that - c
CCBCodeMonkey
02/21/2019, 7:45 PMCopy code
how is this different than what I said? required fields to me are basically a simple validation on the dataThe reason you make it required is for the generated graphql schema and client - c
CCBCodeMonkey
02/21/2019, 7:46 PMI do a lot more complex validations past just required - c
CCBCodeMonkey
02/21/2019, 7:46 PMie string length, alphanumeric, blah blah - c
CCBCodeMonkey
02/21/2019, 7:47 PMagain I am not on the prisma team so you should open an issue or comment with them, I think this is is an issue but not as impactful as your are saying it is - c
CCBCodeMonkey
02/21/2019, 7:47 PMthere is a lot of stuff I would like to see first - d
dan
02/21/2019, 7:49 PMsuper frustrating that I cant just deploy once - d
dan
02/21/2019, 7:49 PMand run migrations - c
CCBCodeMonkey
02/21/2019, 7:50 PMthen switch I guess, I would guess you would find some frustrating issues on pretty much any backend - c
CCBCodeMonkey
02/21/2019, 7:50 PMin terms of level of frustration, that sounds like a 2 to me out of 10 - c
CCBCodeMonkey
02/21/2019, 7:50 PMcompared to other issues I have run into with prisma - c
CCBCodeMonkey
02/21/2019, 7:50 PMlike for example, not being able to have multiple order bys - c
CCBCodeMonkey
02/21/2019, 7:51 PMhttps://github.com/prisma/prisma/issues/62 which I think is way more impactful - c
CCBCodeMonkey
02/21/2019, 7:51 PMor not being able to add fragments on prisma bindings - c
CCBCodeMonkey
02/21/2019, 7:51 PMthose are the biggest things i'd like to see - c
CCBCodeMonkey
02/21/2019, 7:52 PMor ordering by sub fields - c
CCBCodeMonkey
02/21/2019, 7:53 PMor being able to extend your schema in your apollo server layer(which works but is hacky)