µTest
Slick
Our great sponsors
µTest | Slick | |
---|---|---|
2 | 17 | |
478 | 2,636 | |
-0.6% | 0.1% | |
4.2 | 8.6 | |
2 days ago | 4 days ago | |
Scala | Scala | |
- | 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.
µTest
-
From First Principles: Why Scala?
Let's clarify some points for folks not so familiar with Scala.
> * Scala minor version are binary incompatible, so maintaining Scala projects is a big pain. Upgrading Spark from Scala 2.11 to Scala 2.12 was a massive undertaking for example.
Scala just chose a strange naming scheme. Other languages would have just increased their major version instead. The scala minor version is increased every few years and not every month or so.
> * Scala has tons of language features and lets people do crazy things in the code.
Actually, that's not true. Or rather: compared to what language?
Scala has surprisingly few language features, but the ones it has are very flexible and powerful. Take Kotlin for example. It has method extensions as a dedicated feature. Scala just has implicits which can be used for method extension.
> * Scalatest is stil used by most projects and is annoying to use, as described here: https://github.com/lihaoyi/utest#why-utest. The overuse of DSLs in Scala is really annoying.
I agree with the overuse of DSLs. Luckily that got much better, but older libraries like scalatest still suffer from that.
> * Li's libs (os-lib, upickle, utest) have clean public interfaces, but most Scala ecosystem libs are hard to use, see the JSON alternatives for examples
I think that just comes from using the library in a non-idiomatic way. In most applications, you will need to use the whole json anyways, and then you use (or can use) circe like that:
{
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).
-
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?
ScalaMock - Native Scala mocking framework
doobie - Functional JDBC layer for Scala.
Diffy
Quill - Compile-time Language Integrated Queries for Scala
scalaprops - property based testing library for Scala
ScalikeJDBC - A tidy SQL-based DB access library for Scala developers. This library naturally wraps JDBC APIs and provides you easy-to-use APIs.
Scala Test-State - Scala Test-State.
Squeryl - A Scala DSL for talking with databases with minimum verbosity and maximum type safety
Gatling - Modern Load Testing as Code
Clickhouse-scala-client - Clickhouse Scala Client with Reactive Streams support
Scalive - Connect a Scala REPL to running JVM processes without any prior setup
Sorm - A functional boilerplate-free Scala ORM