Kbase P113587: SQL defined timestamp data type changes into datatime data type in 10.1A
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
21/02/2006 |
|
Status: Unverified
SYMPTOM(s):
SQL defined timestamp data type changes into datatime data type in 10.1A
SQL defined Timestamp field in pub schema is created as datetime in 10.1A pub schema
When comparing 10.0B SQL created pub.schema that has a timestamp field against a 10.1A pub schema that was created with the same SQL script, the field is dropped and re-created as datetime data type in the incremental df utility.
CAUSE:
In 10.1A it was decided that the SQL timestamp data type should be called the same as the 4GL data type datetime. When creating a column defined as a timestamp, it will be created as a datetime. If the 10.1A database is compared to an exact database created in 10.0B or earlier, the incremental df file will contain a drop of the column as timestamp and be re-created as a datetime column.
FIX:
This is a known issue and being investigated by development.
Workaround.
Review your schema and if producing an incremental df file between 10.1A or high and 10.0B or lower databases created via SQL, look for any drop and add syntax for the timestamp columns. If any are present and there have been no changes to that field, remove the drop and add syntax from the incremental df file.