Re: Generated columns with user calc -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

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

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.