In a scenario where the database table columns don...
# orm-help
j
In a scenario where the database table columns don't align exactly with how a form on the front-end is setup what is the best solution? As I see it there are two main options: 1) The graphql-yoga schema is consistent with the database and it's up to the front-end to parse and map the attributes from and to the server when fetching or saving. 2) The graphql-yoga schema is setup to match what the front-end dictates and then the yoga server maps back-and-forth when saving and fetching from the db. Is one solution better than the other?