Welcome to Litebase 👋 Share your thoughts, questions, and ideas!

[tlaverdure]

Thanks for checking out Litebase! This is just the beginning. If you’re curious, excited, or even skeptical, I’d love to hear from you.

This discussion is a place to:

• Ask early questions about how Litebase works
• Share ideas or feedback
• Let me know what use cases you're thinking about
• Tell me what feels confusing, surprising, or promising

Whether you're thinking of using Litebase or just exploring the project, your input will help shape where it goes from here.

Looking forward to hearing from you!

[eznix86]

Amazing project!

Can we use Litebase for OLAP?

Can we do multitenancy?

Is the issue drop foreign key constraint solved or it is still there?

[tlaverdure]

Hey @eznix86 thanks for stopping by!

Can we use Litebase for OLAP?

As of right now, OLAP out of scope. The current goal for this project is to be a great general purpose OLTP database. I've had some ideas of adding something of the sort, but honestly it would probably require adding something like DuckDB in the mix since SQLite's B-Tree storage architecture is not suitable for column oriented storage.

Can we do multitenancy

Yes, Litebase will be able to handle multi-tenancy. You have two main options: a single database with a tenant key at the table level for simplicity, or a separate database for each tenant for stronger isolation and easier scalability, which aligns with the plan to tier storage to object storage.

Is the issue drop foreign key constraint solved or it is still there?

Currently Litebase creates an SQLite database connection with foreign key constraints ON. We could leave this up to developers to configure using PRAGMA foreign_keys = ON, but with SQLite you have to ensure this is enabled each time you open a connection. I want to make using this database as easy as possible, and I don't want developers to have to think about sending this pragma each time the send a request. However, this is definitely something that should be configurable at the database level. Once database settings are stable via SQL or CLI you should be able to make the choice and Litebase will manage setting this up as needed when a connection is opened.

Great questions, thanks!

[eznix86]

Thank you very much, for the last element what i was refering to is when you do "FOREIGN KEY(id) REFERENCES Table(id)". You cannot execute drop command to delete that, the only way is to create a temporary table and reconstruct the table without this foreign key.

Does this keep SQLite as is, or add an improvement on top of SQLite?

This is what i am refering to: laravel/framework#51373 (it is a workaround in Laravel, as it is part of SQLite behaviour).

[tlaverdure]

Thanks for the clarification. This project would keep SQLite as is in this sense. There are some limitations that this project cannot tackle in terms of what SQLite supports. Maybe one day, we'll see.