AdHocTables

From Mu2eWiki
Revision as of 14:15, 15 May 2025 by Rlc (talk | contribs) (Created page with "==Introduction== The primary conditions database functionality is to store and deliver detector calibrations which are relevant for certain intervals of validity. Sometimes there is a need to store additional information that doesn't fit into this format. For example, saving a record of when and how certain calibrations were taken, what entries are historically related to each other, or other notes and history. ''ad hoc'' tables were implemented to m...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Introduction

The primary conditions database functionality is to store and deliver detector calibrations which are relevant for certain intervals of validity. Sometimes there is a need to store additional information that doesn't fit into this format. For example, saving a record of when and how certain calibrations were taken, what entries are historically related to each other, or other notes and history. ad hoc tables were implemented to meet this need.

We expect the content will be related to maintaining conditions data, and not truly arbitrary, since it is store din the conditions database.


Implementation