Author SHA1 Message Date
dc 49443134b1 blog: document the concurrency caveat of two librefs over one table
mp_lockanytable keys its control table on (lock_lib, lock_ds), and the
approve service takes that lock on the base table named in the submit
record. The MPE_DATALOADS staleness check is keyed the same way. So two
registrations of one physical file neither lock nor observe each other,
and a second approval can overwrite the first silently.

Spell that out, note that the hook route routes both mirrors to one base
table and so does not have the gap, and give the two ways to close it.
2026-09-24 17:08:53 +00:00
allan 1119645a00 Merge pull request 'blog: add a post on running two rule sets against one table' (#20) from feed/two-rule-sets-one-table into main
publish / Build-and-publish (push) Successful in 4m19s
Reviewed-on: #20
2026-09-24 16:37:16 +00:00
dc a1513b871e blog: add a post on running two rule sets against one table
Capture all four screenshots against a licensed instance, so the
free-tier licence banner is no longer in frame.
2026-09-24 16:34:29 +00:00

Diff Content Not Available