G
George Potemkin
Guest
Since V11 Progress by default calculates what seems to be an alternate (SQL) CRC: _File._Fil-res1[1] It’s an addition to 4GL CRC: _File._CRC. Article: Format of field _File._Fil-res1 is too short for values in OpenEdge 11 Progress KB - Format of field _File._Fil-res1 is too short for values in OpenEdge 11 FOR EACH _File: DISPLAY _File._Tbl-Type _File._File-Name _File._Fil-res1[1] FORMAT ">>>>>>9" _File._CRC. END. Both values are evenly distributed in the range from 0 to 32K. Both are not applied to SQL Views (_Tbl-Type = “V”). Both are changing if we are modifying a table structure. But they are not equal. I guess these CRCs are calculated based on the different sets of field properties. For example, 4GL CRC uses 4GL data type (_Field._Data-Type) while SQL CRC uses SQL data type (_Field._Fetch-Type). Is it correct? Can we use SQL CRC to track the changes of the tables that are ignored by 4GL CRC? Or do they always change synchronously? For example, if we change a field type from “integer” to “int64” then SQL type will be automatically changed from “integer” to “bigint”. So both CRCs are changed.
Continue reading...
Continue reading...