From 44497ff189bb4fd8c5f495e0147078f3dc3aa9a7 Mon Sep 17 00:00:00 2001 From: Salvatore Di Guida Date: Fri, 6 May 2016 13:38:53 +0200 Subject: [PATCH] Added comment in IOVEditor::flush concerning the update policy. --- CondCore/CondDB/src/IOVEditor.cc | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/CondCore/CondDB/src/IOVEditor.cc b/CondCore/CondDB/src/IOVEditor.cc index a29fb6ff0e7d9..ce5d53b555234 100644 --- a/CondCore/CondDB/src/IOVEditor.cc +++ b/CondCore/CondDB/src/IOVEditor.cc @@ -182,7 +182,11 @@ namespace cond { if( m_data->iovBuffer.size() ) { std::sort(m_data->iovBuffer.begin(),m_data->iovBuffer.end(),iovSorter); cond::Time_t l = std::get<0>(m_data->iovBuffer.front()); - if( m_data->synchronizationType != cond::SYNCH_ANY && m_data->synchronizationType != cond::SYNCH_VALIDATION ){ + //We do not allow for IOV updates (i.e. insertion in the past or overriding) on tags whose syncrosization is not "ANY" or "VALIDATION". + //This policy is stricter than the one deployed in the Condition Upload service, + //which allows insertions in the past or overriding for IOVs larger than the first condition safe run for HLT ("HLT"/"EXPRESS" synchronizations) and Tier0 ("PROMPT"/"PCL"). + //This is intended: in the C++ API we have not got a way to determine the first condition safe runs. + if( m_data->synchronizationType != cond::SYNCH_ANY && m_data->synchronizationType != cond::SYNCH_VALIDATION ){ // retrieve the last since cond::Time_t last = 0; cond::Hash h;