ishandotpage
Joined 3 years ago
Joined 3 years ago
It's missing lots of features like sleeping on waits, warm starts etc.
I will not be trusting Cloudflare with anything production critical.
For most purposes, it works perfectly fine, but with two main caveats:
1. It is single user, single connection (i.e. no MVCC) 2. It doesn't support all postgres extensions (particularly postGIS), though it does support pgvector
https://github.com/supabase-community/pg-gateway is something that may be used to use pglite for prototyping I guess, but I haven't used this.
System maintainers / stakeholders themselves need to come up with a "Definition of Working"
Since distributed systems are basically in some state of failure/degradation almost all of the time, it is useless to try to say that "the system is working when there are no errors anywhere".
Some sort of threshold needs to be arrived at where we can say "it's working".
What that threshold looks like is going to vary from project to project.
I'm not a fan of the enterprisey hexagonal-style code this generates, but I can understand where this might be useful for someone who does follow that.
A question regarding evolution: it's rare that schemas stay constant. I'm not sure if this tool will lend itself well when the time comes to, say, add another table, though I might be misunderstanding here.
Not one has given me the correct answer yet.
They usually get it if I prefix the prompt with "Please continue the tongue twister"
Mastodon: @[email protected] Website: https://ishan.page