Issue is present in the ExtractTable class for Sybase ASE 15+. The computed column definition is extracted from the syscomments text field. This field is of varchar(255) and the table will hold multiple records for an object that has a definition of more then 255 length. currently extraction is expecting only one record per column, need to modify extraction to be aware of the multi record return per column.
Extraction modified to correctly create the computed column information. Columns information will be distinct now and we will no longer trim the computed source. We can do regression testing on all versions of sybase ase but only truely affects v15+
Extraction modified to correctly create the computed column information. Columns information will be distinct now and we will no longer trim the computed source. We can do regression testing on all versions of sybase ase but only truely affects v15+
Verified in ADS v17.0.3-16. Now works correctly in Script Full, Schema Script Generator and ER Diagram Generator
Verified in ADS v17.0.3-16. Now works correctly in Script Full, Schema Script Generator and ER Diagram Generator
The fix for this issue causes an issue in versions of sybase 12.5 and below where the datatype is getting set to calculated because the columns computed text returns a single character black space. Due to this the datatype is scripted as an single character blank line. I have fixed the extraction and have tested to make sure this original issue is still fixed and that the extraction will not consider an empty string as a computed field.
The fix for this issue causes an issue in versions of sybase 12.5 and below where the datatype is getting set to calculated because the columns computed text returns a single character black space. Due to this the datatype is scripted as an single character blank line. I have fixed the extraction and have tested to make sure this original issue is still fixed and that the extraction will not consider an empty string as a computed field.
scripting of table object column's datatype should script correctly now for all versions of sybase
scripting of table object column's datatype should script correctly now for all versions of sybase
Issue #14345 |
Closed |
Fixed |
Resolved |
Completion |
No due date |
Fixed Build v17.0.7-4, v18.0.0-devi-192 |
No time estimate |
Issue is present in the ExtractTable class for Sybase ASE 15+. The computed column definition is extracted from the syscomments text field. This field is of varchar(255) and the table will hold multiple records for an object that has a definition of more then 255 length. currently extraction is expecting only one record per column, need to modify extraction to be aware of the multi record return per column.