On Sun, 2 Jun 2002, Brent Kearney wrote:
> I was using sql-ledgers v1.6.9. After unpacking 1.8.4 over top, and
> clicking the 'Upgrade Dataset' button (after filling out the pgsql
> username & password fields), I get message, "All Datasets up to date!".
I had the exact same problem yesterday. After some investigation I gave up
and simply hacked the progrma to be less obnoxious about which databases
to upgrade.
Dieter: I imagine the source of the problem lies in using a more strict
access to the postgres server than the average setup (never allowing
master access from the web browser, only a specific account holding all
ledger databases, and the use the suexec feature of Apache to run as that
same user).
Beware that this can ruin non-postgres databases hosted on the same
postgres server. But then again - you get a second screen where you can
unselect wrongly selected databases by hand before you do the actual
update (and you DID use separate login for each set of databases and avoid
master login from a browser, right?).
Attached is the diff that made it work for me.
- Jonas
--
Jonas Smedegaard (+45 40843136) http://dr.jones.dk/~jonas/
Spiff ApS (= IT-guide dr. Jones ApS) http://dr.jones.dk/
Debian GNU/Linux developer http://people.debian.org/~js/
--- User.pm.orig Thu May 30 04:19:02 2002
+++ User.pm Mon Jun 3 12:32:17 2002
@@ -400,8 +400,7 @@
if ($form->{dbdriver} eq 'Pg') {
$query = qq|SELECT d.datname FROM pg_database d, pg_user u
- WHERE d.datdba = u.usesysid
- AND u.usename = '$form->{dbuser}'|;
+ WHERE d.datdba = u.usesysid|;
my $sth = $dbh->prepare($query);
$sth->execute || $form->dberror($query);
