From the PostgREST readme. Even if you generated the controllers with openapi, I'm not aware that openapi will generate you an entire application already hooked up to the db?
> guess this is only as true as saying that you have to deal with Erlang because you use RabbitMQ. Or you have to deal with C because you use PostgreSQL. Same applies with PostgREST, you don't have to write Haskell to use it, only SQL.
In my experience you will undoubtedly end up dealing with the oddities of it as some point. Would you rather deal with oddities in Haskell or in C? For most of the world, for better or worse, C (or Go or Java) is probably more pragmatic.
I did not know about openapi-generator. Very interesting.
But what's the benefit of having PostgREST involved in this scenario?
> PostgREST wrap your database but don't generate code they just run in memory.
PostgREST generates an OpenAPI output, which in turn can generate code with tools such as openapi-generator[1], Go being one of the many langs supported.
> (and you have to deal with Haskell and Erlang)
I guess this is only as true as saying that you have to deal with Erlang because you use RabbitMQ. Or you have to deal with C because you use PostgreSQL. Same applies with PostgREST, you don't have to write Haskell to use it, only SQL.
[1]: https://openapi-generator.tech