HOW-TO for SOAP?

[fjf2002]

Now that I have (almost) everything mentioned in https://github.com/PostgREST/postgrest/issues/2188, I can use SOAP.

Suggestion: I could add a HOW-TO for SOAP to the documentation?

By the way, I have noticed you have released PostgREST-Version 9.0.1 at docker hub, but without my XML PRs #2202 and #2300. Will they come later?

[steve-chavez]

but without my XML PRs #2202 and #2300.

@fjf2002 Note that 9.0.1 actually doesn't contain any new feature, only fixes. We did it because a user was asking for a patch release and me and Wolfgang discussed that it's not ideal to do two consecutive major releases, we should provide at least one without a breaking change(patch or minor version release).

Will they come later?

Of course, I just need to provide a way forward from a breaking change I introduced. Then it would be good to release v10 and it will include all of the unreleased features.

Suggestion: I could add a HOW-TO for SOAP to the documentation?

That would be amazing. I'm also interested in that one. Please go ahead!

[steve-chavez]

@fjf2002 Btw, note that the latest pre-release does include the unreleased features. It's uploaded on dockerhub too.

• https://github.com/PostgREST/postgrest/releases/tag/v9.0.0.20220531
• https://hub.docker.com/layers/postgrest/postgrest/postgrest/v9.0.0.20220531/images/sha256-243482ed04fa99e115a003be226743e1edc31d4bcd42ee1652d3a6a3ba69cf18?context=explore

[fjf2002]

Thanks for the clarification. https://github.com/PostgREST/postgrest/pull/2300 is still missing in v9.0.0.20220531, but no need to hurry.

[fjf2002]

Concerning the SOAP How-To:

@steve-chavez: Well, er, when posting on topic https://github.com/PostgREST/postgrest/pull/1582, I made wrong claims. I have corrected that:

EDIT: Well, it seems that I have mixed up different stuff. The correct answer is: As a workaround, I add Accept: text/xml in the reverse proxy, when making the request.

The thing is, the average SOAP request is made without a line Accept: text/xml. So the SOAP How-To would include this dirty "add Accept: text/xml in the reverse proxy, when making the request" stuff.

The other solution would of course be, solving https://github.com/PostgREST/postgrest/pull/1582, at least the case with single unnamed xml parameter and scalar xml return value.

What do you think?

[steve-chavez]

The thing is, the average SOAP request is made without a line Accept: text/xml. So the SOAP How-To would include this dirty "add Accept: text/xml in the reverse proxy, when making the request" stuff.

@fjf2002 I see. The above would be acceptable, the how-to for img also has some Nginx stuff(removed on latest)

The other solution would of course be, solving https://github.com/PostgREST/postgrest/pull/1582, at least the case with single unnamed xml parameter and scalar xml return value.

I've also added a coment on https://github.com/PostgREST/postgrest/pull/1582#issuecomment-1154431651, perhaps we can move it forward with that.

[fjf2002]

Meanwhile, this SOAP docs are active. Closing ticket.