RE: Request for CL, DDS, SQL RPG enhancements

["Joep Beckeringh" <joep@xxxxxxxxxxxxxxxxxxx>]

Rob,

Number one reason is indeed the referencing in display files. The main
concern is whether a field needs a sign or not. Things like that should
not be left to the programmer of the day.

I don't quite see how we could solve this particular problem by using
UDT's.  But then again, it is not much of a problem as long as we keep
using DDS :-)

Oh, and eh, please don't tell anyone, but we do use numeric fields for
dates.  Proper date fields may be fine theoretically,  but the handling
of non-required fields is a pain.  And no, we are not too keen on null
values.

Joep Beckeringh


> -----Oorspronkelijk bericht-----
> Van: rpg400-l-admin@midrange.com
> [mailto:rpg400-l-admin@midrange.com] Namens rob@dekko.com
> Verzonden: maandag 22 april 2002 15:58
> Aan: rpg400-l@midrange.com
> Onderwerp: RE: Request for CL, DDS, SQL RPG enhancements
>
>
> This is a multipart message in MIME format.
> --
> [ Picked text/plain from multipart/alternative ]
> Just trying to understand where you are concerned with the
> sql editing. Is
> it in:
> Having your screen DDS adopt the editing of the DB definition?
> Having your printer DDS adopt the editing of the DB definition?
> Being able to type in RUNQRY QRYFILE(mylib/myfile) and having
> the numerics
> edited?
>
> Also, being short on time precludes me from answering my own
> question but
> instead of defining your fields as DEC or whatever, would
> using a UDT get
> what you need?
> ...
> DECIMAL (DEC)
>     A decimal number. ...
> ...
> distinct type
>     The name of an object that exists on the system, type *SQLUDT,
>     which contains type information.  This can be library qualified.
>       Length and Scale cannot be specified.
>
> On the not so lighter side:  Please don't tell me you have an
> 8 or 9 digit
> field in which you use an edit word to get 2002-04-22.  Or a
> 6 digit field
> to get 04/22/02.  They have date fields for this stuff.
>
> Rob Berendt