attempting to do:
// sidenote. thrilled to have learned GraphQL. kind of confused how/why to integrate it with vercel?
error:
no error yet just looking at this example CREATE TABLE route
to avoid sounding lazy:
the wondering is if someone knew they were deploying directly to vercel from the start
why not just do the INSERT INTO commands and skip making graphql/resolvers.ts that mutate local postgres DB data
recursion of being decently graphQL proficient is worth it but if the goal was to iterate fullstack UI concepts at fastest speed
skip working local?
proposed approach:
perhaps put these in pages/api and have resolvers perform queries (which to vercel are INSERT INTO commands)
attempting to do: // sidenote. thrilled to have learned GraphQL. kind of confused how/why to integrate it with vercel?
error: no error yet just looking at this example CREATE TABLE route![Screen Shot 2023-08-01 at 1 02 09 AM](https://github.com/frankcollins3/Next-Water-App/assets/73137934/8708b157-cf74-4734-8369-ad1c5c3c7198)
to avoid sounding lazy: the wondering is if someone knew they were deploying directly to vercel from the start why not just do the INSERT INTO commands and skip making graphql/resolvers.ts that mutate local postgres DB data
recursion of being decently graphQL proficient is worth it but if the goal was to iterate fullstack UI concepts at fastest speed skip working local?
proposed approach: perhaps put these in pages/api and have resolvers perform queries (which to vercel are INSERT INTO commands)