The ns_db as redefined in nsdb/compat.tcl
is required to create/access the metadata. Though the latest nspostgres
re-added a lot of functionality lost in 3.0, it didn't add enough to make
it work with nsadmin.
[Moss, Tim]
Yep, realized the historical reasons for doing it this way -
however with AOLserver v4 there seems to be some problem with this
redefinition - the new ns_db exists, but the original one from the nspostgres
driver was lost. It seems as if the rename to c_ns_db
failed. Since c_ns_db doesn't exist the new ns_db
command was failing.
I wanted to see if it was going to work at all with
v4 so I just renamed the new ns_db proc and changed all references to it in
the nsadmin code, and the new proc calling the original ns_db rather than
trying to rename it to c_ns_db.
This allowed the admin pages to be displayed (didn't
get anything previously), but then as soon as I got to the stage of selecting
a pool in the DB/Admin/ pages I hit the problem I originally
mentioned.
The first thing you should do after
installing nsadmin it is to create a new db for each of your pools.
You can delete it later if needed. This will build the ns_columns and
ns_tables tables for the metadata. After that, restart aolserver.
Without those two tables, NOTHING is going to work correctly.
[Moss, Tim]
Yep this
was a clean/empty database. ns_columns and ns_tables already existed (exmpty
though) from when I'd run nsadmin with AOLserver
3.5.2
