SQL-Ledger Homepage

SQL-Ledger User Forum

Forum index page

Log in | Register

Back to the forum
Board view  Mix view

Bug in {dbconnect} (General)

posted by clusters(R), 02.06.2015, 18:06

Ok...further testing I found the port parameter to be removed from the members file for the user after I did a save preference. I could manually update the members file and the connection will reestablish; however, once I did a save preference again the port parameter will be removed and connection was lost...
so save preference would left out the port parameter of the dbconnect string...

any idea any one please?

Version is 3.0.8 that I am testing...

I have Postgres 9 running on a non-default port as the default was used by
Postgres 8.

When I create a new user the user can't login as the {dbconnect} is missing
the port parameter. I can't seem to find where that is set. I tried
updating the user conf file manually including the members file but the
member file would get over written without the port no...so no go...any


Complete thread:

Back to the forum
Board view  Mix view
1007 Postings in 335 Threads, 363 registered users, 95 users online (0 registered, 95 guests)
SQL-Ledger User Forum | Admin contact
powered by my little forum