Keep cached dataset descriptions current
What It Does
A description-affecting table changes and a later query or description request resolves that metadata. Person-specific authorization is applied after reading reusable workspace metadata.
The Flow
The writing transaction’s table trigger advances the affected workspace stamps or the global stamp. Read workspace and global stamps, construct the key, then check memory and the shared cache. On a miss, resolve registry and workspace configuration and cache the result under the key already read. Old entries expire rather than receiving invalidation messages.
When Something Fails
Trigger failure rolls back its transaction. The stamp cannot commit independently of that write. A failing cache read is handled as a miss. The request can proceed through metadata resolution instead of failing on cache availability. A cache-store error does not prevent returning the resolved result. Concurrent metadata changes can span these reads; the recorded consistency gap remains.
Idempotency and Concurrency
Stamp sequence values are not reused after rollback. Writing identical cache content under one key is harmless, but a stable key does not prove snapshot-consistent resolution. Stamps and metadata are read separately. No common database snapshot or final stamp recheck ensures that concurrent metadata writes yield an internally consistent cached description.