Phil Longstaff writes:
>> Turns out port 0 is hard coded.
>>
>> I changed src/backend/dbi/gnc-backend-dbi.c line 438 from this:
>>
>> result = dbi_conn_set_option_numeric( be->conn, "port", 0 );
>>
>> to this:
>>
>> result = dbi_conn_set_option_numeric( be->conn, "port", 5432 );
>>
>> and things
On May 18, 2009 10:27:45 pm Scott Peshak wrote:
> > I hate to reply to my own post, but I did a little more digging on this.
> > Gnucash is trying to connect to port 0 for some reason. I confirmed
> > this with wireshark. I tried adding :5432 to the host text field, but
> > this had no effect.
>
> OK. I found the problem. The dbi is specifying port 0. The default for
> postgres is 5432, so I can easily change it to that. For a non-default
> installation, I'm not sure how the user should specify the port.
>
I vote for allowing : in the host field. (and assume 5432 if
it is omitted) I
On May 18, 2009 09:33:44 pm Scott Peshak wrote:
> On Mon, May 18, 2009 at 7:44 PM, Phil Longstaff wrote:
> > Does anything show up in your gnucash trace file?
>
> Yep:
>
> * 17:22:14 CRIT [gnc_dbi_postgres_session_begin()]
> Unable to connect to
> postgres://postgres.otherhost.local:gnucash:gnuc
> I hate to reply to my own post, but I did a little more digging on this.
> Gnucash is trying to connect to port 0 for some reason. I confirmed
> this with wireshark. I tried adding :5432 to the host text field, but
> this had no effect.
Turns out port 0 is hard coded.
I changed src/backend/d
On May 18, 2009 10:01:04 pm Phil Longstaff wrote:
> On May 18, 2009 09:33:44 pm Scott Peshak wrote:
> > On Mon, May 18, 2009 at 7:44 PM, Phil Longstaff
wrote:
> > > Does anything show up in your gnucash trace file?
> >
> > Yep:
> >
> > * 17:22:14 CRIT [gnc_dbi_postgres_session_begin()]
> > Unab
On Mon, May 18, 2009 at 8:33 PM, Scott Peshak wrote:
> On Mon, May 18, 2009 at 7:44 PM, Phil Longstaff wrote:
>
>>
>> Does anything show up in your gnucash trace file?
>
> Yep:
>
> * 17:22:14 CRIT [gnc_dbi_postgres_session_begin()]
> Unable to connect to
> postgres://postgres.otherhost.local:gn
On Mon, May 18, 2009 at 7:44 PM, Phil Longstaff wrote:
>
> Does anything show up in your gnucash trace file?
Yep:
* 17:22:14 CRIT [gnc_dbi_postgres_session_begin()]
Unable to connect to
postgres://postgres.otherhost.local:gnucash:gnucash:password: -2
* 17:22:28 CRIT g_hash_table_destroy: as
On May 18, 2009 06:33:39 pm Scott Peshak wrote:
> I just built 2.3.0 to test the new DBI features. When I tried to save-as
> my current (xml) data file to postgres I got the following error:
>
> Can't parse the URL
> postgres://postgres.othermachine.local:gnucash:gnucash:password
>
> Both my usern
