Re: Change to dbRecordsOnceOnly?

[Andrew Johnson via Tech-talk <tech-talk at aps.anl.gov>]

On 5/10/23 10:58 AM, Han Lee via Tech-talk wrote:

Hi Michael,

Could you help me figure out how to use this dbRecordOnceOny within a st.cmd?

var dbRecordsOnceOnly 1

It affects dbLoadRecords() and dbLoadTemplate() commands that come after it.

- Andrew

On Wed, May 10, 2023 at 8:53 AM Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov> wrote:

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

--

Jeong Han Lee, Dr.rer.nat.

Staff Scientist and Engineer

Cell: +1 510 384 3868

https://orcid.org/0000-0002-1699-2660

-- 
Complexity comes for free, Simplicity you have to work for.