Open saurabhgssingh opened 1 year ago
Hey @saurabhgssingh! The main purpose of using sqlite
for aim
was to ship the package as a whole and not require any external stuff. With the next major release we can also provide a way to provide the url of your own database. As currently in versions 3.x
we have 2 sqlite databases one is used for UI and the other one for SDK, but with version 4 we're planning to drop one, and it will be much easier to provide an option for external db url.
So, which day it will be released? @mihran113 Thanks a lot.
As currently in versions 3.x we have 2 sqlite databases one is used for UI and the other one for SDK, but with version 4 we're planning to drop one, and it will be much easier to provide an option for external db url.
Hi @mihran113 Is this change still going to happen?
I'm subscribing to this issue as well. I think it would be a huge improvement to be able to swap sqlite for Postgres/MySQL as sqlite is very much not production-ready. I've have had multiple issues with sqlite when I tried to deploy Aim on our GKE cluster.
@mihran113 I would appreciate if we can have a better visibility on whether this is going to happen at all. I can see that Aim is already using sqlalchemy
, so it might not be impossible to switch to a more matured DB. And if there is any incentive/direction from the core maintainers, I'd like to help with this.
🚀 Feature
Do we have the capability to change the sqllite database used as backend to something like postgres or mysql
Motivation
The sqllite database causes unwanted issues such as lockage when trying to use on kubernetes servers