When launching the client it returns: ======================================= No database found, you must create one! ======================================= Neither admin nor demo logins work. Reproducible: Always Steps to Reproduce: 1.Emerge dev-db/postgresql-8.0.13 2.Emerge app-office/tinyerp-server-4.0.3 3.Emerge app-office/tinyerp-client-4.0.3 4.Complete the ebuild post install config scripts; e.g. # emerge --config =app-office/tinyerp-server-4.0.3 5.Launch tinyerp-client 6.Fails to connect with error: "No database found, you must create one!" Expected Results: It should offer to login with a choice of databases (in this case the default db terp). The # emerge --config =app-office/tinyerp-server-4.0.3 post-install script creates a database called terp, but under the user name postgres (superuser). To fix it I had to run: =============================================== $ su postgres Password:************ $ cd $ psql -l List of databases Name | Owner | Encoding -----------+----------+----------- template0 | postgres | SQL_ASCII template1 | postgres | SQL_ASCII terp | postgres | SQL_ASCII (3 rows) $ dropdb -U postgres terp DROP DATABASE $ createdb -U terp terp CREATE DATABASE $ $ psql -l List of databases Name | Owner | Encoding -----------+----------+----------- template0 | postgres | SQL_ASCII template1 | postgres | SQL_ASCII terp | terp | SQL_ASCII (3 rows) $ exit $ su Password:************ # /etc/init.d/tinyerp-server start ===============================================
You can create the database in the client menu. This is the normal behavior of the application.
Thanks Cedric, it wasn't clear to me and could not see it in the Docs that this is what I had to do to connect first time. It would be more straight forward if the post-install config script created the necessary database and user to enable first time connections. From different forums I see that I am not alone in having difficulty with this. Since this is perhaps more of a feature request than a bug, I apologise for the noise. -- Regards, Mick
