Experimental Physics and
Industrial Control System

Marty Kraimer <[email protected]> · Wed, 07 Jan 1998 15:48:49 -0600

William Lupton wrote:
> 
> Dear all,
> 
> Marty wrote:
> > First of all this is not a new restriction in 3.13. The limit was always
> > there. before 3.13 no error message was issued if the string was too long.
> > The error message is somewhat misleading because the truncated string is
> > written.
> 
> Can we just suppress the warning message?
> 
> If we don't want to lose the ability to report on more serious truncations,
> can we define a new optional .dbd field that controls whether the warning
> is reported on a per-field basis, e.g.
> 
>         field(DESC,DBF_STRING) {
>                 prompt("Descriptor")
>                 promptgroup(GUI_COMMON)
>                 truncwarn(0)
>                 size(29)
>         }
> 
> with a default truncwarn value of 1? Or does this require changes to internal
> data structures that one would rather not change?
> 
> William

It does require changes to internal data structures. Also think of
precedent being set.
Will we have an endless set of xxxwarn attributes for each field
description?

Note also that the warning message is telling the application engineer
that he/she has given a value that will not appear as specified in the
database. It really is a database configuration error.

Marty Kraimer

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System