| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 <2023> 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 <2023> 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: Change to dbRecordsOnceOnly? |
| From: | Han Lee via Tech-talk <tech-talk at aps.anl.gov> |
| To: | Michael Davidsaver <mdavidsaver at gmail.com> |
| Cc: | EPICS Tech-Talk <tech-talk at aps.anl.gov> |
| Date: | Wed, 10 May 2023 08:58:45 -0700 |
fyi. There is a proposed change to the meaning of the dbRecordsOnceOnly global variable under consideration.
This change would make dbRecordsOnceOnly!=0 less restrictive.
As a reminder, dbRecordsOnceOnly defaults to zero.
https://github.com/epics-base/epics-base/pull/383
Currently with
> record(ai, "myrec") {}
dbRecordsOnceOnly!=0 currently disallows appending fields with either form:
> record("*", "myrec") {} # error
> record(ai, "myrec") {} # error
This PR changes the meaning such that dbRecordsOnceOnly!=0 always allows appending when explicitly intended (rtype "*").
> record("*", "myrec") {} # allowed
> record(ai, "myrec") {} # error