Re: Trigger question - Null Fields

Thanks John,

I guess I was trying to find out if anyone had actually used them yet and
what their experience was.  There probably won't be much use of them except
for those that come from strictly SQL backgrounds.

----- Original Message -----
From: "John P Carr" <jpcarr@tredegar.com>
>Also, I asked on an earlier post which no one responded to, whether anyone
> >had any experience using the new user defined field objects.  Do you know
> of
> >anyone working with them?  They are very interesting to me, since if  I
> >understand it correctly, we could perhaps move some of the trigger
> >record-level editing on down to the actual field level.
>
> Well there are two things UDT's and UDF's
>
> User Defined Types(UDT) - allow you to define your own data type.
> Classic example is like US_Dollars for example.  You would not
> inadvertently be able to add this field to another plain numeric.
> Remember Native I/O(RPG Read/Write/Update) is not allowed on
> a table(file) with UDT's.   It's SQL or nothing.
>
> User Defined Functions(UDF) - allows you to create your own SQL function.
> Something like a RPG procedure( ie   EVAL  NAME = DAYOFWEEK(DATE) )
> There are 3 flavors;  External, Sourced, and SQL.    For the Sourced & SQL
> types
> you must have SQL and the C compiler on your machine.
>
> Both of these are need V4R4.   I don't see you using them in a typical RPG
> system.
> I will signon to my V4R4 box today and give you more info if you  would
> like.
>
> They are so new(how many people are on V4R4 ?) that not many people have
> real life experience with them.   I will be experimenting with them soon
on
> my
> V4R4 170.  I'll give you feedback if you'd like.
>
> >Also, apparently
> >this is what the rest of the SQL world uses instead of field reference
> >files? Is that correct?  If so, how would you control and/or catalog a
> large
> >number of them.  Create a whole separate library for them maybe?  Also, I
> >assume you have to have the C compiler to write code for them too?
>
> Well the Field Reference thing is still not  SQL friendly.    I still
> believe
> the benefits of a well structured Field Reference with the refer process
> is head and shoulders above anything in SQL.

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---