amforeas
pgsql-http
| amforeas | pgsql-http | |
|---|---|---|
| 1 | 17 | |
| 44 | 1,164 | |
| - | - | |
| 10.0 | 5.8 | |
| almost 2 years ago | 28 days ago | |
| Java | C | |
| GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
amforeas
-
becauseBackendIsJustASocialConstructRight
I feel triggered https://github.com/Eldelshell/amforeas
pgsql-http
- PostgreSQL Is Enough
-
becauseBackendIsJustASocialConstructRight
I don’t understand the question https://github.com/pramsey/pgsql-http
- What are my options to send a notification everytime a new row is inserted into my PostgreSQL RDS database/Aurora database?
-
How to perform authenticated http requests with the http REST client extension?
I am trying to use the supabase http rest client extension to fetch data from an external API. Following the supabase docs and the GitHub repo readme, I have not been able to successfully make a request that requires auth, specifically an API key in the request header with key x-api-key.
-
Sketch of a Post-ORM
- Hasura Remote Schema (https://hasura.io/blog/tagged/remote-schemas/)
If you want more control over the web API and you were going to fetch the data within your Python back-end and process it there, for some use-cases (not all, but some), there are options:
- pg_http (https://github.com/pramsey/pgsql-http)
Life is about trade-offs. Doing the work in SQL is not without its drawbacks, but it's also not without its benefits, and that's true for doing the work in a general-purpose language as well. Whatever the drawbacks of doing it in SQL, one of the benefits has got to be eliminating the impedance mismatch (for people who regard that mismatch as a problem, and the OP seems to be one such person). What I claim is that doing the work directly in the database shouldn't be ruled out in general (the specifics of a given use-case may rule it out in particular) any more the the other common patterns (API hand-written in Python, for instance) shouldn't be ruled out in general.
-
Watching for changes to DB by another app
You could e.g. use the trigger to call http api using e.g. https://github.com/pramsey/pgsql-http
-
How to best fetch JSON data from external API and write to supabase every hour?
I do this all the time just with Postgres functions. Just turn on the following extensions: http (https://github.com/pramsey/pgsql-http) pg_cron (https://github.com/citusdata/pg\_cron)
- What's Postgres Got to Do with AI?
- Edge Functions or Database Functions?
- Pgsql-HTTP: HTTP client for PostgreSQL
What are some alternatives?
HoloDB - HoloDB is an RDBMS seemingly filled with random data. This data does not actually take up any space in memory or on a volume (to use an analogy, it is as if the data set is projected as a hologram from a simple configuration). The base layer is an arbitrarily large, read-only data set that is readable and searchable, and yet fully consistent. Any pieces of data and index lookups are calculated on-the-fly. An optional second layer is built on top of this, allowing read-write access (stores differences while maintains consistency and searchability). You can start an arbitrarily large database in moments, with minimal effort; all you need is a YAML configuration file or some JPA entites.
Multicorn - Data Access Library