GNOME Bugzilla – Bug 332251
Cannot open existing postgreSQL database
Last modified: 2018-06-29 20:58:27 UTC
Please describe the problem: When I try to access an existing database created with gnucash-1-8-12 directly from command line, an error pops up, that the URL cannot be parsed: $ uname -a Linux p49979 2.6.12-gentoo-r9 #3 Sat Dec 10 21:57:30 CET 2005 x86_64 AMD Athlon(tm) 64 Processor 3400+ AuthenticAMD GNU/Linux $ /usr/local/bin/gnucash postgres://localhost/konten2005 gnucash: [M] "Found Finance::Quote version "1.11 Error Pop-up Can't parse the URL postgres://localhost/konten2005. When trying to create a database newly (after loading a gnucash-1.8.12 .xac-file) by the 'save as'dialog, error message pops up 'Error getting information for '/home/klaus/postgres:/localhost': No such file or directory' When trying to open the database from within the menu File-->open ... there is no possibility to enter the 'postgres://localhost/foo' command. Steps to reproduce: 1. /usr/local/bin/gnucash postgres://localhost/konten2005 2. Using under 'save as' the string 'postgres://localhost/foo' 3. Using the File-->open menue Actual results: Expected results: Does this happen every time? Yes Other information:
Other related bug#105235 . The problem with the "save as" dialog is already noted in bug#329802; if that one describes your problem fully, we'd close this one as duplicate. However, if I understand correctly, then it is not even possible to "open" or to open by cmdline argument any existing postgres database. That's of course a major bug, which should hopefully be fixed by 2.0.0. Raising severity because of that.
Are you sure you can't open it by command-line? I thought the problem was only that you couldn't open it via File -> Open or File -> Save As
Sorry, just re-read the bug report. Please ignore comment #2; I'm an idiot and can't read this morning.
Hi Derek, any chance to get the parse error fixed before rel. 2.0.0? I'd like to work with the postgres backend, and gnucash2 would solve alot trouble with utf8 and online banking. So getting it with 1.94 or 1.95 would be nice. Thanks, Klaus
This is confirmed, but I'm not sure if we're going to fix it for 2.0.
Chris wrote: > I could probably fix this bug, but look at bug#313696. The only reason to do anything with pg right now, IMO, would be to allow the immediate export to xml, but that's been impossible at least as far back as 1.8.11. So, IMO, there's no point in fixing this bug unless we're committed to fixing bug#313696 as well, and I have no idea how difficult that would be. :( Due to this, we decided to disable the pg backend in the 2.0.0 release. Sorry for that :-(
Deactivated --enable-sql in SVN r14175. Need to revert r14175 when activating the postgresql backend again.
BTW, I've been working on this a bit the past few days, and I think I'm able to get at least this much working. I'm still seeing if it's enough to allow saving the db to an xml file, though.
Ok, hopefully fixed in r14200. It'd be nice if someone could test this before 2.0. *hint*
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=332251. Please update any external references or bookmarks.