Avelino

Documentation (integration) how to use FDW (Foreign Data Wrappers) + pREST

1

**What is FDW?** read [here](https://wiki.postgresql.org/wiki/Foreign_data_wrappers) FDW connects to an external database (MySQL, MSSQL, Oracle, MongoDB, Kafka, HBase/BigTable, Elasticsearch, ...) and via PostgreSQL connection it is possible to consume data from...

pREST has endpoint for database listing (`/databases`), before listing tables we need to list the database, only after selecting the database we can list the tables

today it is defined in hardcode the name of the database and schema, we need to list this dynamically https://github.com/prest/prest.admin/blob/2d3e258342ec6ec64bf4065ff73dc4c24572ad45/src/pages/index.tsx#L31 pREST Server endpoint: `/databases` ``` { "datname": "prest" } ```...

unit testing without postgres dependency (mock)

2

### Discussed in https://github.com/prest/prest/discussions/562 Originally posted by **avelino** June 23, 2021 The `postgres` adapter depends on the postgreSQL (database) server to run (`go test`), i.e. it was developed with integration...

we have the `_returning` filter (parameter) implemented, but it is not documented - [markdown file](https://github.com/prest/prest/blob/main/docs/query-statements/_index.en.md) - [documentation topic](https://docs.prestd.com/query-statements/#filters-parameters-query-string---get) **implementation code:** https://github.com/prest/prest/blob/3bcad8231f0e9a6c352db5009ba1490cf033f938/adapters/postgres/postgres.go#L282-L296

looking at the `scorecard-trusted` process history it takes an average of ⚠️ **180m**, it doesn't make sense to have an action running on every pull request ([this comment](https://github.com/prest/prest/pull/566#issuecomment-874609859)), **ideally run...

PREST_SSL_MODE is PostgreSQL config not http ssl - and other ssl variables

2

We are using the `PREST_SSL_MODE` variable for ssl configuration of the postgres not http server. The variable name refers to prest's ssl configuration (api rest, i.e. http) not postgres We...

I like the idea of supporting `ltree` field To support this type of fields would be to implement the list of operators (`Table F.13. ltree Operators`), here https://github.com/prest/prest/blob/9b677c30fef3f06f62f8a22cafd55a075655bdbc/adapters/postgres/postgres.go#L1028:L1067 _Originally posted...

**In Postgres 13 and early if you wanted to find all medium shirts that are neon yellow you write some query:** ``` SELECT * FROM shirts WHERE details->'attributes'->>'color' = 'neon...

Endpoint to execute custom query

10

Custom SQL query execution via **POST**, open text based on **SELECT**, will not be accepted ~INSERT, UPDATE and DELETE~. This feature must be chosen enabled in the configuration file, by...