Re: Confused about DDL and DDS

Probably nothing was missed, and the reply is not off mark. The given CREATE TABLE source is a great example of exactly what Rob was emphasizing; that the DDL has the ability to embed the constraint definitions within the CREATE instead of having to add the constraints after the CRTPF.

My reply was actually /thread shift/ where I was bemoaning a perceived slight against non-SQL. I replied even though I knew Rob was merely *encouraging* and *touting* SQL over DDS for CRTPF and ADDPFCST, and presumably that he really does understand that there is no effective difference for constraints [other than the ability to embed them in the create request as with DDL].

My reply was mostly to emphasize to anyone else who might [in the future] read his post and misinterpret; i.e. someone might think they _have to change_ from DDS to SQL, when that is not required; that his wording seemed too dogged to me I prefer to express that when there is a move to DML, then by all means one should strive to use DDL as well. But when an application is all non-SQL then there are or may be several reasons to *not* change to use SQL DDL; i.e. even if there are others who would suggest there is no excuse not to do so. I prefer to warn against doing what might be discovered too late, that a poor decision was made; i.e. finding out only after moving the changes into production, at which time backing out the change becomes very difficult.

Regards, Chuck

Rick.Chevalier@xxxxxxxxxxxxxxx wrote:

I haven't been following this thread for a little while and it looks like I missed something. My apologies if this reply is off
the mark.

If the issue is the use of alter table to add constraints at table creation they aren't necessary. I place the constraints
directly in my create statement.

rob@xxxxxxxxx wrote:

Not one of the samples posted here included any constraints: referential, check or otherwise. All stuff that was impossible with DDS. And can only be tacked on after the fact with ADDPFCST.

The accusation that the constraint information can "only be tacked on after the fact" is disingenuous. That the DDL can
include constraint definitions in the CREATE statement is nice;
great even. <<SNIP>>