Re: Data validation, mapping, and error handling

[Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>]

Aaron Bartell wrote:
> Note that my statements aren't in relation to mapping HTML input fields to
> DB records but instead mapping them to controller program fields.  As I
> understand it, EGL's term of record could be considered similar to an RPG
> data structure on steriods - it's a grouping of fields, but not necessarily
> a DB record.
>   

Not really.  The BasicRecord type is essentially a data structure with 
metadata - all those cool things like prompts and validations that we've 
seen at work today.  However, there are additional features that can be 
specified at the record level: an SQLRecord, for example, will 
automatically generate the appropriate code for CRUD or QUERY events 
without the programmer having to do the dirty work.  An MQSeries record 
will similarly hide the complexity of MQ Series from a programmer.

The Record is a very powerful construct and is perhaps one of the things 
that best exemplifies the 4GL nature of EGL.

Joe