Incident Reports Addressed in 2.10

Incident Reports Addressed in 2.10

The following is a list of the incident reports addressed in version 2.10. Click on the incident # in order to view the details of the incident report.

Serious Problems

Build

#

Title

Workarounds

1	3604	Using More Than One Correlated Condition in a Correlated Sub-Query Causes Incorrect Results	No
1	3606	Text Indexes Containing Words Longer than Word Length Can Experience Corruption	No
1	3607	LIKE with a Percent (%) Wildcard Followed by an Underscore (_) Wildcard Returns Incorrect Results	No
1	3608	Creating Indexes On Temporary Tables Causes a Catalog Update	No
1	3609	Altering a Table Created with CREATE TABLE..AS SELECT Can Cause Corruption Error	No
1	3611	SQL Aggregate Calculations Can Differ Between EXEs and DLLs	No
1	3612	Optimized LIKE Conditions with Leading Percent (%) Wildcard Can Cause Incorrect Results	No
1	3613	Optimized CONTAINS Conditions with Leading Asterisk (*) Wildcard Can Cause Incorrect Results	No
1	3615	Querying ServerSessions Table Causes #506 Error When a Long-Running Process is Taking Place	No
1	3616	Computed Columns Not Updating Immediately When Dependent Columns Are Modified	No
1	3617	Generated Columns Not Updating Properly for Remote Sessions	No
1	3618	RUNSUM() Aggregate Queries Not Being Reset Properly When Underlying Data Changes	No
1	3620	Committing a Large Transaction with Ordered Inserts Can Cause Stack Overflow	No

Minor Problems

Build

#

Title

Workarounds

1	3610	Recompiling ElevateDB Manager with Delphi XE2 for ANSI Usage Causes AV During File Load/Save	No
1	3614	Millisecond Interval Literals Using 4 Decimal Places Instead of 3	No
1	3619	ERRORMSG Function Documentation Incorrectly Refers to ERRORCODE Function	No

More Support Options

Search Incident Reports

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals