Re: SQL DDL and field reference file.

rob@xxxxxxxxx wrote:

If I create a simple field reference file like this:
CREATE TABLE rob/fref ( SomeAmt dec(11,2) , check (SomeAmt>0) , SomeText char(30) , check (SomeText<>' '));
LABEL ON COLUMN ROB/FREF (
SOMEAMT IS 'Line one',
SOMETEXT IS 'line Two');

Then I use the field reference file like thus:
create table rob/sampletbl as (
select SomeAmt, SomeText from rob/fref) with no data
It does bring the column headings along. However is
there also a way to get it to bring the constraints along?

Probably not of interest [no ability to choose columns], but that example is easily replaced by a CL request to: CRTDUPOBJ FREF ROB *FILE ROB SAMPLETBL DATA(*NO) CST(*YES) TRG(*NO) FILEID(*NO)

The limitation for not carrying constraints is obvious when they are more complex. If the UNIQUE constraint included both columns but only one is carried into the new TABLE, then how would that work? If the CHECK constraint tested more than one column, if one of those columns was not carried to the new TABLE, then how would that work?

Regards, Chuck