Attachment: exception-with-messages-more-than-133-bytes.sql.7z [ 12952 ]

Attachment: exc-long-crash-FB_40-on-extracting-metadata.PNG [ 12953 ]

Version: 3.0.0 [ 10740 ]

Version: 2.5.5 [ 10670 ]

Version: 2.5.4 [ 10585 ]

Version: 2.5.3 Update 1 [ 10650 ]

Version: 2.1.7 [ 10651 ]

Version: 2.5.3 [ 10461 ]

Version: 2.5.2 Update 1 [ 10521 ]

Version: 2.5.2 [ 10450 ]

Version: 2.5.1 [ 10333 ]

Version: 2.5.0 [ 10221 ]

assignee: Dmitry Yemanov [ dimitr ]

description: Apply script from attached .7z to empty database and then run ISQL -X.
On 2.5.6 and 3.0.0 - all works fine.
On WI-T4.0.0.150:
1) when source script contains only two exceptions (with message length = 133 & 134 bytes) - second ("exc_test_b") will NOT be extracted.
2) when source script contains all three (i.e. code for "exc_test_c" is active) - ISQL crashes with screen that is in attached .png

=>

Apply script from attached .7z to empty database and then run ISQL -X.
On WI-T4.0.0.150:
1) when source script contains only two exceptions (with message length = 133 & 134 bytes) - second ("exc_test_b") will NOT be extracted.
2) when source script contains all three (i.e. code for "exc_test_c" is active) - ISQL crashes with screen that is in attached .png

summary: Extracting metadata (ISQL -X): regression in 4.0. Exception with message length = 134 bytes not present in log, with length = 135 causes ISQL crash => ISQL -x may crash while exporting an exception with message text length > 127 bytes

Attachment: exc-long-crash-FB_40-on-extracting-metadata.PNG [ 12953 ] =>

description: Apply script from attached .7z to empty database and then run ISQL -X.
On WI-T4.0.0.150:
1) when source script contains only two exceptions (with message length = 133 & 134 bytes) - second ("exc_test_b") will NOT be extracted.
2) when source script contains all three (i.e. code for "exc_test_c" is active) - ISQL crashes with screen that is in attached .png

=>

Apply script from attached .7z to empty database and then run ISQL -X.
On WI-T4.0.0.150:
1) when source script contains only two exceptions (with message length = 133 & 134 bytes) - ISQL silently crashes (only the first exception is exported)
2) when source script contains all three exceptions (i.e. code for "exc_test_c" is active) - ISQL crashes with a Windows screen

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.5.6 [ 10721 ]

Fix Version: 3.0.1 [ 10730 ]

Fix Version: 4.0 Alpha 1 [ 10731 ]

status: Resolved [ 5 ] => Resolved [ 5 ]

QA Status: No test => Done successfully

status: Resolved [ 5 ] => Closed [ 6 ]