kotlin-result
SQLDelight
Our great sponsors
kotlin-result | SQLDelight | |
---|---|---|
35 | 32 | |
936 | 5,917 | |
- | 1.8% | |
8.8 | 9.6 | |
5 days ago | 2 days ago | |
Kotlin | Kotlin | |
ISC License | Apache License 2.0 |
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.
kotlin-result
-
JEP draft: Exception handling in switch
Author here. I have no idea what you could possibly mean with this comment. The coroutineBinding implementation correctly uses the coroutines API for parallel decomposition of Result bindings, exactly how the Kotlin Corotines guide tells you to (backed by a [Mutex](https://github.com/michaelbull/kotlin-result/blob/master/kot...)). The coroutineBinding isn't even the main selling point of the library, you can use it without using this feature entirely.
Please could you elaborate on what "looking thread safe" means to you? The only portion of the library that supports concurrency *is* thread safe - the unit tests prove it and the use of concurrency primitives such as Kotlin's Mutex are indicative of this. I truly have no idea how you've judged the entirely of the lbirary on whether it's "thread safe" when there is a single function that's related to concurrency and it is very clearly using concurrency primitives.
-
How do you define errors?
Sealed classes in combination with a library like https://github.com/michaelbull/kotlin-result will get you what you need. Essentially at that point you'll be doing error handling the way you would in Rust, where a 1-level deep sealed class containing data classes as children act as the root error type and each of its variants. If you have errors coming from two different domains you just create a wrapper error type for each domain.
-
Result Class with Generic Type for both Success and Failure States
This is a great result lib: https://github.com/michaelbull/kotlin-result
-
Is runCatching in use in any of your projects ? My team is abusing it
Lastly I do not like kotlin's Result and we use the kotlin-result library which is more expressive and not tied to Throwable (similar to Arrow's Either).
-
Struggling with software robustness with Kotlin
In my own code, I started to use explicit error handling. I'm currently experimenting with Result (from https://github.com/michaelbull/kotlin-result) and Raise (from https://arrow-kt.io/).
-
Thoughts on Kotlin Multiplatform?
un-related to multiplatform i've found it extremely helpful to wrap things in a Result type. If something can throw an error, it get's a Result return type. It sounds like that would help your use case too. The built in Result may be useful too
-
Programming with Result
This is a better impl.
- It seems like I'm forced to make this choice at least once a day
-
Are nearly all your functions suspend?
Using a result type can help to differentiate quite nicely. https://github.com/michaelbull/kotlin-result
-
Kotlin Nitpicks: Language and Standard Library
kotlin-result
SQLDelight
-
querky – autogenerate Python functions and types for your SQL queries
This seems to be similar to https://github.com/cashapp/sqldelight, and I've always wanted a python equivalent!
In typescript, there are query builders (not talking about ORMs) that can basically do this within the type system, but that would be infeasible in python's type system. This approach (type/code generation is a good alternative, though I like using sqlalchemy / alembic to manage schemas/migrations.
One thing I'm curious about is how it knows the types of columns? I looked quickly at the Readme but didn't see it (probably a parameter somewhere I missed).
- I'm creating a REST API using KTOR. What's the best ORM to go with KTOR ?
-
KMM alternatives to Android Datastore & Room DB?
That functionality has existed for almost exactly a year
-
What were your negative experiences when adopting KMM?
- SQLDelight - great experience overall, the only issue that I found, was when that I made a database migration that worked on Android, but not on iOS (https://github.com/cashapp/sqldelight/issues/3812)
-
Adopting Kotlin Multiplatform Mobile(KMM) on 9GAG App
Database - SQLDelight
-
Android Starter Template (hilt, ktor, coroutines, flow, modules, gradle.kts, version catalog, compose, MVVM, tests, GitHub CI)
room is a great example but like I said our data is kotlin-only so we tend to use libraries like sqlDelight.
-
Announcing new crate - "hugsqlx": turning SQLx queries into Rust functions
This seems similar to https://cashapp.github.io/sqldelight/ for kotlin, I think this approach is pretty neat, good luck with it!
-
ADVICE WANTED - Typescript PostgreSQL without ORM
Sounds like you want what SQLDelite offers, but for TypeScript. SQLDelite is only for Kotlin and SQLite though.
-
Why We're Moving on from Firebase
SQLDelight had neat built in support for this
https://cashapp.github.io/sqldelight/
-
Flyweight: An ORM for SQLite
You would really like sqldelight[1] then. It takes the concept of an ORM and flips it on its head. Instead of mapping function calls to SQL statements, it lets you write SQL statements and then generates classes for you that have methods for those statements.
For instance, you could have a SQL statement like getCardsForFight: select * from fights where cardId = ? and titleFight = ?, and it would generate a class that has a method getCardsForFight(cardId: number, titleFight: number).
[1]: https://github.com/cashapp/sqldelight
What are some alternatives?
result4k
Exposed - Kotlin SQL Framework
kotlin-monads - Monads for Kotlin
Realm Asset Helper - A small library to help with Realm.IO integration in Android apps
Result - The modelling for success/failure of operations in Kotlin and KMM (Kotlin Multiplatform Mobile)
Ktorm - A lightweight ORM framework for Kotlin with strong-typed SQL DSL and sequence APIs.
Arrow Meta - Functional companion to Kotlin's Compiler
jOOQ - jOOQ is the best way to write SQL in Java
Komprehensions - Do comprehensions for Kotlin and 3rd party libraries [STABLE]
RoomAsset - A helper library to help using Room with existing pre-populated database [DEPRECATED].
Kategory - Λrrow - Functional companion to Kotlin's Standard Library
Realm - Realm is a mobile database: a replacement for Core Data & SQLite