SQLDelight VS ObjectBox Java (Kotlin, Android)

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).

That functionality has existed for almost exactly a year

- 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)

Database - SQLDelight

room is a great example but like I said our data is kotlin-only so we tend to use libraries like sqlDelight.

This seems similar to https://cashapp.github.io/sqldelight/ for kotlin, I think this approach is pretty neat, good luck with it!

Sounds like you want what SQLDelite offers, but for TypeScript. SQLDelite is only for Kotlin and SQLite though.

SQLDelight had neat built in support for this

https://cashapp.github.io/sqldelight/

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

When I first attempted to publish to F-Droid, I experienced several pipeline issues. After reading through the pipeline logs in GitLab, I realized that my application's database (ObjectBox) was not entirely FOSS compliant and was causing build failures. The following day was spent migrating my app to Room.

I would focus on Kotlin instead of Java, there's really no point in sticking to Java at this point. And when it comes to databases, some local ones that are pretty easy to get into are Realm and ObjectBox, SQLite can definitely be a bit overwhelming at the beginning.

Not sure what exactly the issue is in your case, but linux-aarch64 is already a supported platform for ObjectBox (with some dependencies on libc versions etc). Maybe raise an issue for https://github.com/objectbox/objectbox-java with your specific error output and some details on your setup?

Just to add to this, there's also Realm and ObjectBox as alternatives.

Adding ObjectBox [0] to the list.

[0] https://objectbox.io/

Obectbox

While - strictly speaking - "database" refers to a systematic collection of data, "Database Management System'', or DBMS, refers to the piece of software that provides an efficient and versatile method of working with data(eg: ObjectBox). However, often the term "database" is also used loosely to refer to a DBMS, and you will find most DBMS only use the term database in their name and communication.

Maybe this? I've been looking at it recently.

https://github.com/objectbox/objectbox-java is an alternative to Room.

Here's the issue