[PostgREST] SDK Generation

[Olshansk]

• This was extracted from [PortalDB] POC PostgREST implementation with API and client autogeneration #452 so the first PR focuses solely on the PostgREST API and OpenAPI spec
• This focuses solely on the Go SDK

---

Is this even necessary given that postgrest has compatible SDKs?

https://github.com/supabase-community/postgrest-go

https://docs.postgrest.org/en/v13/ecosystem.html#client-side-libraries

[commoddity]

Is this even necessary given that postgrest has compatible SDKs?

@Olshansk Given our preference for using fully typed code in our Go codebase - and especially avoiding usage of interface{}/any as much as possible - I think the autogenerated Go client SDK provides a far superior API vs the https://github.com/supabase-community/postgrest-go client.

The supabase-community client also doesn't seem to be actively maintained (last release was May 29, 2024).

You can see an example of how the autogen Go client SDK is used here:
https://github.com/buildwithgrove/path-external-auth-server/blob/postgrest-data-source/postgrest/driver.go#L111

As you can see, the client SDK provides a lot more type-safe code with concrete structs, query construction, etc.

So given all of the above IMO we should keep the autogen Go (and Typescript) SDK client.

[commoddity]

Closing this in favour of separate PRs to add the Go & Typescript SDKs in that order.