Re: [Bulk] Format level identifiers on SQL tables?

On 20-Apr-2016 15:34 -0500, David Gibbs wrote:

On 4/20/2016 3:20 PM, Rob Berendt wrote:

In general, anything that changes the length or position of any
fields in the record format used by the program requires that the
program be recompiled.

Yep, that's what I thought too ... but it appears a columns default
value effects it too.

I created a test table with the following SQL:

CREATE TABLE DEVDMGWRK/TEST1
( FIELD1 CHAR ( 10) NOT NULL WITH DEFAULT 'ABC'
, FIELD2 CHAR ( 10) NOT NULL WITH DEFAULT
)

The format level identifier on the table is '1E0C965CBDD7E'.

I then dropped the default from FIELD1

ALTER TABLE DEVDMGWRK/TEST1 ALTER COLUMN FIELD1 DROP default

Now the format level identifier is '1E0C9664BDD7E'.

It seems to me that the default value of a field should have nothing
to do with the format of the file, just its contents.

A different default value is not the change being reflected in the hash by that column attribute change via ALTER [or as seen instead via two separate CREATE requests]. The *lack of a default* for that field was reflected in that change of the hash; i.e. an INSERT is henceforth disallowed on the field FIELD1 after the DROP DEFAULT, versus merely having changed the default from a specific literal to the data-type default.

In effect, that ALTER to the column will have modified the _equivalent_ DDL CREATE to this:

CREATE TABLE DEVDMGWRK/TEST1
( FIELD1 CHAR ( 10) NOT NULL
, FIELD2 CHAR ( 10) NOT NULL WITH DEFAULT
)

Notably different than what the _unchanged_ RcdFmt LvlID would have been, if the effect of the ALTER were instead:

CREATE TABLE DEVDMGWRK/TEST1
( FIELD1 CHAR ( 10) NOT NULL WITH DEFAULT
, FIELD2 CHAR ( 10) NOT NULL WITH DEFAULT
)