-
Notifications
You must be signed in to change notification settings - Fork 351
Clarification - supported DB backends? #650
Comments
Here is a log of a session using a PostgreSQL database and trying to use different projects:
So this is definitely broken. |
Agree, we should than change the documentation to sqlite is the only one at the moment really working |
I'm not sure I understand the problem. If by changing the connection configuration to specify another type of DBMS everything works fine, it is intended behavior. No? |
Hm.. I think my main concern is that the behavior when using SQLite is documented and easily to understand... you run But if you use a different DBMS you have to exit viper, change the .conf file and then run If this is the intended behavior then this should at least be documented (currently there is not mention of changing |
There are some issues that refer to database backends other than SQLite (#583 #573 #302).
The Viper documentation (https://github.com/viper-framework/viper/blob/master/docs/source/usage/concepts.rst) states that:
I tested this on PostgreSQL and also looked through the code. Having more than one database currently only works automatically with SQLite. A workaround is to manually edit the
viper.conf
, replace theconnection
string and restart Viper.viper-update
currently also only takes care of SQLite files.So either we explicitly state that users MUST use SQLite or we add the missing things to the roadmap. What do you think @botherder @Rafiot @deralexxx ?
The text was updated successfully, but these errors were encountered: