Six months in, I would never look back. Once it "clicks", it is a joy to develop. I ditched Sqitch, though (ashamed to say I still did not implemented a db migration system....), and I am still figuring out how to best test my Postgres functions. However, more and more I rely on Postgraphile's auto-created methods to manipulate data on the server, so testing should be less of an issue in the future.
why did you ditch sqitch? lack of utility? I was looking forward to having finally found someone of continuous DB migration (like in laravel).
what's currently also stopping me from pulling the trigger on this, at some point in the future I maybe will wrap this project into electron to deploy it as standalone. and I'm not sure how lightweight, versatile PostgreSQL is on eg windows...
It just felt it was holding me back on fast iterations, as my DB was relatively simple. My plan was to have a base version with all the tables I needed, then create a base migration and go from there. But I never did the "first migration" in the end. I know this will bite me in the ass later, so it is on my TODO list.
GraphQL is actually quite simple once you get the grips of it. I am also planning on trying to write my own schema in my next project, just for practice. You should give it a try, then maybe use SQLite for your Electron project?
You should give it a try, then maybe use SQLite for your Electron project?
Writing my own schema wouldn't be the problem, but I hope that graphile writes all the CRUD and other boilerplate resolvers for me which I hate to do over and over again
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Six months in, I would never look back. Once it "clicks", it is a joy to develop. I ditched Sqitch, though (ashamed to say I still did not implemented a db migration system....), and I am still figuring out how to best test my Postgres functions. However, more and more I rely on Postgraphile's auto-created methods to manipulate data on the server, so testing should be less of an issue in the future.
why did you ditch sqitch? lack of utility? I was looking forward to having finally found someone of continuous DB migration (like in laravel).
what's currently also stopping me from pulling the trigger on this, at some point in the future I maybe will wrap this project into electron to deploy it as standalone. and I'm not sure how lightweight, versatile PostgreSQL is on eg windows...
thanks for further elaborating btw!
It just felt it was holding me back on fast iterations, as my DB was relatively simple. My plan was to have a base version with all the tables I needed, then create a base migration and go from there. But I never did the "first migration" in the end. I know this will bite me in the ass later, so it is on my TODO list.
GraphQL is actually quite simple once you get the grips of it. I am also planning on trying to write my own schema in my next project, just for practice. You should give it a try, then maybe use SQLite for your Electron project?
Writing my own schema wouldn't be the problem, but I hope that graphile writes all the CRUD and other boilerplate resolvers for me which I hate to do over and over again