ProditionsCode: Difference between revisions
Jump to navigation
Jump to search
(Created page with " ==Introduction== ==Adding an Entity== ==Entities depending on other entitites==") |
No edit summary |
||
| Line 1: | Line 1: | ||
==Introduction== | ==Introduction== | ||
ProditionsService provides conditions data "entities". It is a layer of code over the DbService and is the principle user interface for accessing conditions data. It allows the creating and caching quantities derived from DbService database tables and other Proditions entities, creating an unlimited stack of database-derived quantities. It will sense if a derived quantity is out of date, because the run/subrun changed and the underlying input data changed, and update itself as the user accesses the entity. | |||
This page will explain how to add a Proditions entity. | |||
==Adding an Entity== | ==Adding an Entity== | ||
==Entities depending on other | |||
==Entities depending on other entities== | |||
[[Category:Computing]] | |||
[[Category:Code]] | |||
[[Category:Conditions]] | |||
Revision as of 19:49, 12 February 2020
Introduction
ProditionsService provides conditions data "entities". It is a layer of code over the DbService and is the principle user interface for accessing conditions data. It allows the creating and caching quantities derived from DbService database tables and other Proditions entities, creating an unlimited stack of database-derived quantities. It will sense if a derived quantity is out of date, because the run/subrun changed and the underlying input data changed, and update itself as the user accesses the entity.
This page will explain how to add a Proditions entity.