pgsql-http
Slick
pgsql-http | Slick | |
---|---|---|
17 | 17 | |
1,164 | 2,638 | |
- | 0.0% | |
5.8 | 8.7 | |
25 days ago | 6 days ago | |
C | Scala | |
MIT License | BSD 2-clause "Simplified" 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.
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
Slick
- How many people/companies are fully on Scala 3?
-
First Slick prerelease for Scala 3!
Made a PR on slick to document this https://github.com/slick/slick/pull/2760 (workaround is quite easy, you can just define def tupled = (apply _).tupled in the companion object of the case class and it will also compile for all Scala versions).
-
Sketch of a Post-ORM
The Scala ecosystem has a few ways to do composable type-safe query building, e.g. Slick[0] or more recently Quill[1]. . I believe both also have ways to do compile-time string interpolation (e.g. sql"""select * from users where id = ${user.id}""") which generate prepared statements (I know Slick does prepared statements. Quill has similar macros but I haven't looked into how safe they are to use).
[0] https://scala-slick.org/
-
Slick 3.5.0-M3 has been released
Release notes at https://github.com/slick/slick/releases/tag/v3.5.0-M3
-
Database abstraction library which allows a clean domain model
With all this in mind, I landed at the first candidate: slick from https://scala-slick.org/ that you all probably know.
-
Scala 3 migration: 7 benefits that outweigh the risks
I think Slick's current priority is also getting in Scala 3 support: https://github.com/slick/slick/issues/2177
-
Slick 3.4.x is here!
Future releases might not be announced here. To get notified, go to https://github.com/slick/slick, click the Watch dropdown button at the top, select Custom, check Releases, and click Apply.
-
Is there any good resource for learning Slick (3.x)?
https://github.com/slick/slick/pull/2097 now I use slightly lower version of slick so this might be an upgrade that resolves (I do recall using it in 21 and it was still buggy and I filed a ticket, which I cannot find at the moment), but given a complex enough query (we have one in PROD which has tons of flexibility in terms of filters that can be passed in) but it also makes for complex code.
-
Slick 3.4.0 is imminent
I started writing a reply but then I realized it would be long and depends on exactly what you mean, so maybe it's better to post the question in https://github.com/slick/slick/discussions/categories/questions?
-
Scala: A Love Story
I purchased the very entertaining book Seven Languages in Seven Weeks. Although I found Haskell fascinating and tempting, I knew it was unrealistic to introduce it in our company. Scala on the other hand looked like it could be the holy grail: All the characteristics I was looking for, no need to abandon the JVM and its cornucopia of tools and libraries, and the possibility for coexistence with Java and therefore incremental adoption. After implementing some simple programs to identify any immediate risks of committing to the language and its ecosystem, I started to introduce Scala in customer projects. Luckily, I was fortunate enough to work with open-minded, curious, and ambitious team members who were also experienced enough to appreciate the benefits of the language. We immediately applied our experience with functional programming, and embraced immutability. Libraries like Slick and Akka HTTP (we actually started out with its predecessor, Spray) made building database-backed REST services a breeze. And the resulting code was robust and highly maintainable. Scala's expressive type system and type inference made it easy to build a restrictive, consistent domain model without bloating the code. There was virtually no overhead. Any boilerplate could be easily abstracted out. In the end, the application code felt natural, concise and elegant. Programming was fun again.
What are some alternatives?
Multicorn - Data Access Library
doobie - Functional JDBC layer for Scala.
supabase-mailer - Send and track email from Supabase / PostgreSQL using a Transactional Email Provider
Quill - Compile-time Language Integrated Queries for Scala
pg_net - A PostgreSQL extension that enables asynchronous (non-blocking) HTTP/HTTPS requests with SQL
ScalikeJDBC - A tidy SQL-based DB access library for Scala developers. This library naturally wraps JDBC APIs and provides you easy-to-use APIs.
graphile-engine - Monorepo home of graphile-build, graphile-build-pg, graphile-utils, postgraphile-core and graphql-parse-resolve-info. Build a high-performance easily-extensible GraphQL schema by combining plugins!
Squeryl - A Scala DSL for talking with databases with minimum verbosity and maximum type safety
amforeas - A RESTful Interface to your database
Clickhouse-scala-client - Clickhouse Scala Client with Reactive Streams support
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
Sorm - A functional boilerplate-free Scala ORM