Re: SQL TABLES vs CRTPF objects

[John Carr <74711.77@xxxxxxxxxxxxxx>]

RE:     Re: SQL TABLES vs CRTPF objects

I asked Kent Milligan of IBM DB2/400 to once again to settle the discussion.
I just got this reply from him that he was kind enough to offer. 
(My suspicions I think were correct about PF's and TABLES being the same 
internally <John Carr>):


Kent said;

The underlying physical object created by CRTPF & SQL CREATE TABLE interfaces
is identical, but their are a few minor differences in terms of object
attributes.

 The underlying object does have an SQL table tag that is set for files created
with the SQL CREATE TABLE statement (this is displayed on the DSPFD command).
The SQL file object also is only allowed to have one member as your example
showed as well as no maximum size.

SQL file object also use the reuse deleted records option by default.
Journaling is only automatically started on the file if the SQL table is
created in a library/collection when that same library has a journal named
QSQJRN.  Default is to journal both before & after images.

SQL tables have more data validation/correction performed on Insert/Update
operations which allows for slightly faster retrieval since the data was
verified on the way into the object.  Conversely, physical file insert/update
operations don't perform this low-level data validation/correction and insert
perform the data verification on the retrieval operations.  This is a slight
performance difference.



Kent Milligan, DB2/400 Solutions Team
AS/400 Partners In Development

+---
| 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
+---