Re: IDDU, S36 & AS/400 SQL & RPG -Reply -Reply

>>> Richard Baird 12/09/97 12:38pm >>>
Scott Cornell wrote:
<snip>
> SQL tables can not have more than one member, even though SQL
> can access multiple member "CRTPF" files using OVDBF.

Richard Baird wrote:
> The differences you site have more to do with SQL syntax
> compatibility than differences in the database.   

> The create table and crtpf bot create DB2-400 database files. 
> but SQL, being a cross platform language, doesn't know what a
> multi member file is, because that's a 400 specific file type.  the
> ovrdbf command more or less "explains" the concept to SQL.

Absolutely true - however, what I was referring was not SQL's
ignorance of members, but the basic underlying difference between a
file object and a table object. To wit, the following is not possible,
even though the OVRDBF part is legitimate:

1) SQL - CREATE TABLE FRED (SOME_DATA NUMERIC)
2) SQL - INSERT INTO FRED (SELECT SOME#S FROM SOMEWHERE)
3) OS/400 - ADDPFM FRED MBR(SECOND)
4) OS/400 - OVRDBF FRED MBR(SECOND)
5) SQL - INSERT INTO FRED (SELECT SOME#S FROM               
           SOMEWHERE_ELSE)

The ADDPFM pukes, giving a CPF message stating that one can't have
multiple members in an SQL table.  Sooo, to use OO terminology,
OS/400 probably defines an SQL table as a child object of an
AS/400 file object (not a instance thereof), inheriting all the
properties of a file object, but having at least one (possibly more?)
of it's own unique properties (or maybe files are children of tables
with the added property of multiple members?)

Scott Cornell
Mercy Information Systems
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@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
+---