Re: Generated columns with user calc

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Joe, I suspect that DDS will not be back-modified to support anything 
DDL can do - kind of a stated position from IBM, right?

Doctor, will I be able to play the piano after the operation?

OK, you probably know that one!

Vern

On 4/28/2021 11:57 AM, Joe Pluta wrote:
> Once again, I'm in a position where I'm doing something that hurts. 
> ("Doctor, it hurts when I do this..." "Well, don't do that!")  I have 
> an SQL defined file with a timestamp.  However, it's specified as 
> TIMESTAMP(0).  I'd like to create a DDS-defined file that mirrors 
> this.  However, it I can't seem to find a way to specify the optional 
> length for a timestamp field (type Z), so it used the default of 
> TIMESTAMP(6) which creates a larger field.
>
> Does anyone know if I can do this? Plan B is to use DDL, which should 
> probably have been Plan A anyway, but now this has become personal.  :)
>
> On 4/28/2021 6:34 AM, Rob Berendt wrote:
> > Great thinking out of the box although I'm not sure a fieldproc will 
> > do it.  I get the idea that it will be called only if that column is 
> > changed.  So if I have a table with COLa, COLb, COLc and I make a 
> > fieldproc over COLc where it is the product of COLa * COLb and I 
> > change the value in COLa it won't fire off an action against COLc.
> > I think you might need a trigger instead.
> >
> > I may be wrong on FIELDPROC.
> >
> > Rob Berendt