Currently when a register starts it invents itself a guid, which is used in the User.register column to detect when a user moves from one register to another.
Apart from the transient entries in User.register, these guids aren't stored anywhere. Tools that watch the Users table (eg. the new "monitor" subcommand) can't display any further information about the register a user has moved to.
We could add a table of till instances, with primary key being the register guid and additional columns being things like software version, startup time, configuration name and terminal name, to enable more information to be displayed. A row would be added to this every time the register is started.
Possibly we could make User.register be a relationship to the instances table?
The instances table could be purged once entries are eg. a month old.
Currently when a register starts it invents itself a guid, which is used in the
User.register
column to detect when a user moves from one register to another.Apart from the transient entries in
User.register
, these guids aren't stored anywhere. Tools that watch the Users table (eg. the new "monitor" subcommand) can't display any further information about the register a user has moved to.We could add a table of till instances, with primary key being the register guid and additional columns being things like software version, startup time, configuration name and terminal name, to enable more information to be displayed. A row would be added to this every time the register is started.
Possibly we could make
User.register
be a relationship to the instances table?The instances table could be purged once entries are eg. a month old.