On L, 2005-10-01 at 08:23 +0000, Andreas Pflug wrote:

> No problem with that (would need two tables, sl_adminnode and
> sl_adminpath). Unless this goes into a 1.1.2, we'll have a gap of
> administrability between 1.0 and 1.2.

Another thing that would be generally interesting from the
administrating point of view would be admin command log, perhaps in a
table called sl_admincmdlog, which stores all commands that were issued,
together with what happened to them. This would be really beneficial in
post-factum debugging of the abundance of footguns there still are left
in slonys admin (create/subscribe/drop node/set/table) command
processing.

actually we should beed something like this

create table X.sl_admincmd (
cmd_id serial primary key,
cmd_node int,
cmd_time timestamp,
command text
);

create table X.sl_admincmdlog (
log_id serial primary key,
log_cmd int references X.sl_admincmd (cmd_id),
log_node int,
log_proceventno int,
log_proctime timestamp,
log_procresult text
);

So it will be much simpler to decipher what has happened once something
gets screwed up.

-- 
Hannu Krosing <hannu at skype.net>