PostgreSQL would be a good candidate IMO

PostgreSQL would be a good candidate IMO

I agree but I think the best consideration is to support ORM, something like SQLAlchemy ORM. As long as we adhere to Object Relational Mapper compatible statements, many major databases could be supported! SQLAlchemy presently supports a variety of dialects including PostgreSQL, MySQL and MariaDB, SQLite, Oracle, and Microsoft SQL Server.

@lainedfles I am in full agreement that we need a more flexible solution to data storage, but I get real nervous about ORMs, heard too many horror stories of absolutely unhinged monstrosities of queries full of JOINS being emitted by them. They can make writing the code easier, but it's usually at the cost of efficiency.

Postgres would be the best use case here.

Any update on this one? Where is the data being handled to be stored in database? at /rag/utils.py ?

Any update on this one? Where is the data being handled to be stored in database? at /rag/utils.py ?

Not sure whether you are talking about storing the information relating to connecting to the database but I do not believe this path has any relation to that.

I am currently looking at creating relational diagram based off of the models located at backend\apps\web\models. I also believe SQLAlchemy ORM is the best option to implement this from a relational database perspective.

Would there also be considerations for something like Mongo in the future?

Would there also be considerations for something like Mongo in the future?
@sfn-git

IMO, MongoDB isn't appropriate for the practical use case here as Open WebUI database is well defined and structured