Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Incident Reports » Incident Reports Addressed in 2.22 |
Build | # | Title | Workarounds |
1 | 4347 | Dropping Database Objects While Querying System Information Tables Can Cause Incorrect Error | No |
1 | 4348 | Queries on Views Not Using the Correct Index for Optimization When Column Correlation Names Used | No |
1 | 4352 | Importing Data into a Table from CSV File Not Handling NAN and INF Literals Properly | No |
1 | 4355 | SQL STDDEV Function Not Working Correctly with DECIMAL/NUMERIC Columns | No |
1 | 4356 | Altering a Primary Key Constraint and Dropping the Last Column Can Corrupt the Key Index | No |
1 | 4359 | ElevateDB to ElevateDB Migrator Not Working Correctly | No |
1 | 4361 | ElevateDB VCL DCU Files for 64-Bit Delphi 10 Seattle Can Experience Random AVs | No |
2 | 4365 | Descriptions of Database Objects Like Tables, Views, Functions/Procedures Not Being Updated Properly | No |
2 | 4367 | Derived Tables in Queries Can Cause a Dangling Read Lock on the Database Catalog | No |
Build | # | Title | Workarounds |
1 | 4353 | ElevateDB Manager Binary BLOB Editor Not Scrolling Properly with Hot Thumb Tracking | No |
1 | 4357 | Missing Flow Control Identifiers Causing Incorrect Error Message | No |
1 | 4358 | Query Optimizer Incorrectly Relying on Index Scan that has High I/O Cost for File-Sharing Access | No |
1 | 4360 | Time Values with Zero Seconds and Non-Zero Milliseconds Converted Incorrectly to String | No |
1 | 4362 | Extended Clauses for CREATE/ALTER TABLE Statements Not Being Parsed Correctly | No |
This web page was last updated on Monday, August 19, 2024 at 05:55 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |