Perhaps the upgrade sql could use a value of "1" for editor and creator for those pre-existing actor.usr rows? Or not.
I believe the new editor and new creator columns should be a SQL foreign key references to actor.usr.id, don't you agree? Null might be OK actually, now that you mention it.
Upon row insert, the creating_workstation column could be populated with actor.workstation.id. The creating org unit could be equal to the actor.workstation.owning_lib.
Is there an issue with these ideas?
Michele - actor.usr already has create_date and last_edit_date.
Mike,
Perhaps the upgrade sql could use a value of "1" for editor and creator for those pre-existing actor.usr rows? Or not.
I believe the new editor and new creator columns should be a SQL foreign key references to actor.usr.id, don't you agree? Null might be OK actually, now that you mention it.
Upon row insert, the creating_ workstation column could be populated with actor.workstati on.id. The creating org unit could be equal to the actor.workstati on.owning_ lib.
Is there an issue with these ideas?
Michele - actor.usr already has create_date and last_edit_date.