My version about postgrest-openapi

[wayland]

While I'm at it, where do the PostgREST dev people hang out? I've gone to #postgrest on FreeNode (still there), and it didn't exist. Is there somewhere else where people hang out?

I'll usually only be active on Saturdays in Australia.

For the record, the Servers stuff is coming along nicely.

HTH,

[laurenceisla]

Hi there! Glad to have you collaborating to the project!

I was going a slightly different direction, in that I was using PL/pgsql

I think we'll need to use the PL/pgsql language for more complex queries than the ones we have now (e.g. to get the embedded resources info), so it's OK to use it.

I added a table for defining servers, so that if people want to define extra servers [...] However, this assumes that we want config in the database.

I was thinking about moving the configuration variables related to OpenAPI from PostgREST to table/function in this extension, it may be defined as JSON values and the servers could go here. I'm not sure if this is the way to go, though, but you can implement it with the table as you mentioned and we can adapt it later if we need to.

I assumed that the API version was not the version of PostgREST, but the version of the API itself -- every time the JSON text for the API changed, the version number should change.

Ah, you're right, it distinguishes the API implementation from the document version (emphasis mine):

The version of the OpenAPI document (which is distinct from the OpenAPI Specification version or the API implementation version).

So, yeah, x-software would be better here. Go for it!

[steve-chavez]

While I'm at it, where do the PostgREST dev people hang out? I've gone to #postgrest on FreeNode (still there), and it didn't exist. Is there somewhere else where people hang out?

We have https://app.gitter.im/#/room/#begriffs_postgrest:gitter.im, which uses Matrix. I've seen some IRC/Matrix bridges too.

For the record, the Servers stuff is coming along nicely.

Cool!