Icon New Incident Reports for 2.17

The following is a list of the new incidents reported for version 2.17. Click on the incident # in order to view the details of the incident report.

Serious Problems

14050Step Over Functionality Not Working in ElevateDB Manager Script DebuggerNo
14064COUNT * Not Working Properly when WHERE Clause Contains Correlated Sub-QueryNo
14073Reverse-Engineering Functionality Not Using Correct Dependency Order for TriggersNo
14082Configuration Log Events Can Become Stuck and Stop Reflecting New Events after RefreshNo
14086IMPORT TABLE Statement Can Experience AV with QUOTE CHAR of #0 (Null)Yes
14105Join Optimizer Not Selecting Optimal Join Orders Based Upon Available IndexesNo
14106Changing a Column Name Included in a Foreign Key in the Alter Table Dialog Can Cause AVNo
14107Freeing a Query with Manually-Locked Rows Can Result in Dangling Row LocksYes
14108Attempting to Rename a Database to an Existing Database Corrupts ConfigurationNo
14145Cannot Use the CAST() Function to Convert a String into a BLOB Value for InsertionNo

Minor Problems

14058Reverse-Engineered SQL for Stores Not CorrectNo
14074Saved Invalid Filter Expressions in ElevateDB Manager Preventing Proper Table OpensNo
14078Character Set Setting Not Being Save Properly for ODBC DSNsNo
14100Changing the Node Display Type in the ElevateDB Manager Explorer Can Cause Access ViolationNo
1410264-bit Issues with ElevateDB Manager Source CodeNo
14103COUNT Function Not Working Properly with Non-Table QueriesNo
14104Invalid Date Values Allowed into Stored Procedure ParametersNo
14109Cannot Access NEWROW Columns from FETCH Statement in BEFORE INSERT TriggersNo