This is one of several limitations that have existed from the start. We have a preliminary plan that we will present at the meeting at KEK. The short answer to handling this as well as the limited string length problem is that we plan to do it in version 4. This is 2 years away according to the plan. It requires at least a rewrite of the database access layer.
Bob
-----Original Message-----
From: Marty Kraimer [mailto:[email protected]]
Sent: Tuesday, November 23, 2004 5:13 AM
To: Dirk Zimoch
Cc: TECHTALK
Subject: Re: only 16 enum states?
Dirk Zimoch wrote:
> Hi all,
>
> when I try to read the choices of an enum field, I only get the first
> 16. This ist not enough to read all the choices of the LINR field
> (menuConvert) if there are many breakpoint tables. It's even not
> enough to read all choices of the STAT field.
As you found out it is a problem in db_access.h, which describes that
data that passes through Channel Access.
>
> Is there a fix?
No.
>
> What happens if I change in db_access.h
>
> #define MAX_ENUM_STATES 16
>
> in
>
> #define MAX_ENUM_STATES 255
You will break any existing CA client and server that uses ENUMs
>
> ?
>
>
> Dirk
>
Perhaps Bob Dalesio can make a few comments about how we plan to address
this and other known problems created by db_access.h. For example
strings are limited to 40 characters. We hope to start addressing these
issues in the near future.
- Navigate by Date:
- Prev:
Re: only 16 enum states? Marty Kraimer
- Next:
RE: only 16 enum states? Liyu, Andrei
- 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
- Navigate by Thread:
- Prev:
RE: only 16 enum states? Jeff Hill
- Next:
RE: only 16 enum states? Liyu, Andrei
- 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
| 
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·