3. We never return the entire record and have not given this as an option. Many hours of debate went into this at the begining of our project and we finally came to the reailzation that this is not needed, and if we do need everything it is not anymore work, we just call the getters for each field as they are needed.
WiltC@xxxxxxxxxx 10/2/2007 3:33:58 PM >>>
3. I'd never have my DB layer return a LIKEREC/EXTFILE DS. Instead, it'd return a named DS like
ItemRec001 that would be defined in the copy source that included the prototypes. So If you add a
field, you add a new DS with the new format. Basically like IBM's APIs do. Besides which, I very
rarely return the entire record. Doing so isn't needed if you're encapsulating properly and only
makes it to easy to break encapsulation. The only program that really needs most of the fields in a
file is a CRUD application for a master file or a file dump type program.
4. I wouldn't want to hire a programmer who couldn't get a very good idea of what
getNextCustomerOrder() did by looking at the procedures name and how it was being used without looking
at the code behind the procedures.
Charles
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Lim Hock-Chai
Sent: Tuesday, October 02, 2007 3:53 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: MVC in RPG?
3. If you still have to do research on all programs that
uses the DB layer when changing attribute of a field, you are
really not gain much from it. As far as adding new field, it
is only true if your DB layer does not have procedure that
allowed caller to get the entire DS of the file.
Unfortunately, getting the entire DS is a pretty useful
function to have.
4. There are several ways to go around the problem, the
point being that are you really gaining anything from DB
layer? Why replace RPG io functions that all RPG developers
are familiar with with your own io functions that no new
comer can understand without additional trainings?
This e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.
-------------------------------------------------
This email transmission and any documents, files or previous
email messages attached to it may contain information that is
confidential or legally privileged. If you are not the intended
recipient, you are hereby notified that any disclosure, copying,
printing, distributing or use of this transmission is strictly
prohibited. If you have received this transmission in error,
please immediately notify the sender by telephone or return
email and delete the original transmission and its attachments
without reading or saving in any manner.
The Evangelical Lutheran Good Samaritan Society.
---------------------------------------------------------
midrange.com
