Well... although the database loaded alright, it is unusable. I get an empty first page and error messages like:
[14/Mar/2003:23:19:18][5118.4101][-conn0-] Error: dbinit: error(localhost::blog,ERROR: value too long for type character(1)
): 'select sec_rotate_last_visit(8778, 1047680358)'
[14/Mar/2003:23:19:18][5118.4101][-conn0-] Error: Filter sec_read_security_info returned error #1: Database operation "1row" failed (exception NSDB, "Query was not a statement returning rows.")
[14/Mar/2003:23:19:18][5118.4101][-conn0-] Error: tclop: invalid return code from filter proc 'Critical filter sec_read_security_info failed.': must be filter_ok, filter_return, or filter_break
NOTICE: Error occurred while executing PL/pgSQL function sec_rotate_last_visit
NOTICE: line 11 at SQL statement
[14/Mar/2003:23:19:18][5118.4101][-conn0-] Error: Ns_PgExec: result status: 7 message: ERROR: value too long for type character(1)
[14/Mar/2003:23:19:18][5118.4101][-conn0-] Error: dbinit: error(localhost::blog,ERROR: value too long for type character(1)
): 'select sec_rotate_last_visit(8780, 1047680358)'
[14/Mar/2003:23:19:18][5118.4101][-conn0-] Error: Filter sec_read_security_info returned error #1: Database operation "1row" failed (exception NSDB, "Query was not a statement returning rows.")
[14/Mar/2003:23:19:18][5118.4101][-conn0-] Error: tclop: invalid return code from filter proc 'Critical filter sec_read_security_info failed.': must be filter_ok, filter_return, or filter_break
Very annoying....
By the way, I do not expect any of you to have a solution for this... I guess we just have to use the old databases on a different install.
With the databases unable to be loaded into new versions, and postmaster not being allowed to run more than once on a machine, I guess this means you have to ditch all of your data every 1-2 years when software must be updated ;)
In this way, one can only use it as a test environment.
