Re: Definition of a Relational Data Base

Michael,

You can use SQL to create, maintain, and delete the tables. I believe that
counts as a DDL. You can write trigger programs in SQL, RPG, COBOL, CL and
a few other languages I can't think of now. Constraints are there if you
want to use them. It is not the same database as it was 25 years ago. It,
like the PC and the AS400/iSeries/i5, they have all evolved. V5R4 has more
functionality in SQL than V5R3 did.

On 5/16/07, Pantzopoulos, Michael <Michael.Pantzopoulos@xxxxxxxxxx> wrote:

I was recently asked if the iSeries had a data base, or whether our
application used flat files.
I said it had a relational DB, but then I started thinking about the
application's use of the DB.

It's a 25 yo application, and yes it has keyed files (physical as well
as logical of course)and these files are related through foreign keys.
Some logicals of course have select/omit criteria.

But there's no constraints, triggers or procedures being used. There is
no use of DDL. It's all compiled DDS.

That got me wondering if there's a more subtle definition of a
Relational DB.

In other words, would I be correct in repoprting back to this person
(the company architect) that yes we do have a Relational DB but it has
not been implemented in a Relational manner? Or should I just keep my
mouth shut?

Thanks.

Mike Pantzopoulos


"This e-mail and any attachments to it (the "Communication") is, unless
otherwise stated, confidential, may contain copyright material and is for
the use only of the intended recipient. If you receive the Communication in
error, please notify the sender immediately by return e-mail, delete the
Communication and the return e-mail, and do not read, copy, retransmit or
otherwise deal with it. Any views expressed in the Communication are those
of the individual sender only, unless expressly stated to be those of
Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any
of its related entities including ANZ National Bank Limited (together
"ANZ"). ANZ does not accept liability in connection with the integrity of or
errors in the Communication, computer virus, data corruption, interference
or delay arising from or in respect of the Communication."
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.