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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Master DBD file for VisualDCT use |
From: | "Johnson, Andrew N. via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "Manoussakis, Adamandios" <manoussakis1 at llnl.gov> |
Cc: | EPICS tech-talk <tech-talk at aps.anl.gov> |
Date: | Fri, 11 Dec 2020 00:33:13 +0000 |
On Dec 10, 2020, at 5:26 PM, Manoussakis, Adamandios via Tech-talk <tech-talk at aps.anl.gov> wrote:
Every site and potentially every IOC could use a different combination of record types, so I don’t think a community-wide file is likely to be terribly useful. If your IOCs are based on the synApps collection you could probably take the DBD file for the
xxx IOC module and use that, but if not you’ll have to generate your own for your particular set of modules.
One complication is if/when new version of a support module containing a record type gets added that has new fields added which version do you use? That’s why I generally recommend using the DBD file for the specific IOC that you’re designing the database
for.
HTH,
- Andrew
--
Complexity comes for free, simplicity you have to work for.
|