When do i try to connect Kexi to my Postgresql database, it returns me this message error: "Error during starting temporary connection using "template1" database name.".
I found this old thread: viewtopic.php?f=221&t=108331 , but it is without a solution.
I've set: host name, port (default), user, password and i tried to toggle on and off "Use socket file instead of TCP/IP port", but it dind't change.

Useless to say that with another program, such as DBeaver, I have no problems connecting to that database.

Debian 4.19.67-2+deb10u1 (2019-09-20) x86_64 GNU/Linux
KDE Frameworks 5.54.0
Qt 5.11.3

Thank you,
Loris

Hi bloris,
Is this a database created using KEXI?

See A1.2 kexi-project.org/wiki/wikiview/index.php@KexiFAQ.html

Ahhh, i was missing this line "Currently you can not "open" (i.e. connect to) databases created outside of Kexi. You can only import the tables and data." ... mm so there is no way to use Kexy with an external db? I'm unhappy, i wanted to try Kexi....

Thank you,
Loris

You can always import the database (that is, migrate) using the KEXI->Import/Export command. Destination server can be the same pgsql server, just another database. This is sometimes acceptable. If you depend on third-party apps or other users that require the original database name, rename the database first and migrate it to the original name. Format of the imported database is the same, just meta data is added. You will loose any advanced advanced objects in the destination db but tables and simple indices. Advanced means views, complex indices, collations and procedures and so on.

Long-term we want to have it all performed dynamically during opening of the db (in-place), it's clear how to do that, it just costs more to develop this (20%) and test/deploy (80% of work). The wish page is https://bugs.kde.org/show_bug.cgi?id=380088.

Greetings

I can't migrate this database to Kexi, so i think i can't use it...

But thank you to explain me this, probably i will try kexi for personal use in my next projects

Sure thing, migrating for small file-based projects can be more acceptable, for PostgreSQL is less practical.

Feel free to request improvements here in the forum, we greatly benefit hearing from db professionals