The last UPDATE in sql/upgrade/1.2-1.3-manual.sql is:

    UPDATE defaults SET value = '1.2.99' WHERE setting_key = 'version';

and the first login attempt ends with the error:

    Database is not the expected version. Was 1.2.99, expected 1.3.0

So the question is just manually change the version or is there one or 
more steps after 1.2-1.3-manual.sql?

Doing a manual update:

    UPDATE defaults SET value = '1.3.0' WHERE setting_key = 'version';

produces:

    25P02:ERROR: current transaction is aborted, commands ignored until end
    of transaction block

>From apache's log (with the [Sat Oct 08 12:14:58 2011] [error] [client 
127.0.0.1] removed)


DBD::Pg::st execute failed: ERROR:  function check_expiration() does not exist, 
referer: http://localhost/lsmb13/login.pl

LINE 1: SELECT check_expiration(), referer: http://localhost/lsmb13/login.pl
                ^, 
referer: http://localhost/lsmb13/login.pl

HINT:  No function matches the given name and argument types. You might need to 
add explicit 
type casts. at LedgerSMB.pm line 967., referer: 
http://localhost/lsmb13/login.pl

DBD::Pg::st fetchrow_array failed: no statement executing at LedgerSMB.pm line 
968., 
referer: http://localhost/lsmb13/login.pl

DBD::Pg::st execute failed: ERROR:  current transaction is aborted, commands 
ignored until end 
of transaction block at LedgerSMB.pm line 983., referer: 
http://localhost/lsmb13/login.pl

DBD::Pg::st fetchrow_hashref failed: no statement executing at LedgerSMB.pm 
line 985., 
referer: http://localhost/lsmb13/login.pl

DBD::Pg::st execute failed: ERROR:  current transaction is aborted, commands 
ignored until end 
of transaction block at LedgerSMB.pm line 995., referer: 
http://localhost/lsmb13/login.pl

DBD::Pg::st fetchrow_array failed: no statement executing at LedgerSMB.pm line 
996., 
referer: http://localhost/lsmb13/login.pl

DBD::Pg::st execute failed: ERROR:  current transaction is aborted, commands 
ignored until end 
of transaction block at LedgerSMB.pm line 781., referer: 
http://localhost/lsmb13/login.pl

2011/10/08 12:14:58 - ERROR Logging SQL State 25P02, error 7, string ERROR:  
current 
transaction is aborted, commands ignored until end of transaction block, 
referer:
http://localhost/lsmb13/login.pl

ERROR - Logging SQL State 25P02, error 7, string ERROR:  current transaction is 
aborted, 
commands ignored until end of transaction block, referer: 
http://localhost/lsmb13/login.pl

Issuing rollback() due to DESTROY without explicit disconnect() of DBD::Pg::db 
handle 
dbname=lsmb13 at LedgerSMB.pm line 899., referer: 
http://localhost/lsmb13/login.pl


Suggesting that simply flipping 1.2.99 to 1.3.0 after 1.2-1.3-manual.sql 
is not enough.

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Ledger-smb-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel

Reply via email to