A possible bug in the TKS database

Its unconfirmed, but it looks like when I set a table value twice for the same key in the same transaction, it is the first value which is used.

Why did I try this? I'm building up layers of methods and setting a default value at the lower level. Not efficient, but an easy design.

If this is a bug, then either I fix TKS or it should raise an exception. The latter would force efficient code, but could be difficult sometimes to accomodate.

Meanwhile I'm working my way through the generation of the basic descriptor units when a cabinet is created. I've just added a way to set the descriptor on a role and implemented ledger entry key/value pairs (previously headers) as well.

Bill