Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Incident Reports » Incident Reports Addressed in 1.10 |
Build | # | Title | Workarounds |
1 | 271 | Non-Optimized Filters Not Handling NULL or Empty String Field Comparisons Properly | No |
1 | 272 | Secondary Indexes Not Being Updated Properly | No |
1 | 273 | Non-Optimized Where Clause in SQL SELECT Statement Causing an Access Violation | No |
1 | 275 | Using Column Names for ORDER BY Clause Causes a Parse Error | Yes |
1 | 276 | Concatenation of String Fields in SQL Expression Engine Not Working Properly | No |
1 | 277 | Total Size Not Being Correctly Calculated for Concatenated String Fields in SQL Columns List | No |
1 | 278 | String Field with Length Greater Than 250 Bytes Not Working Properly | No |
1 | 279 | Repair Functionality Not Detecting and Dealing with Recursive BLOB Pointers Properly | No |
1 | 280 | Database System Utility Reverse Engineering Improperly Referring to ftBinary Field Type | Yes |
1 | 281 | Filtering or Locating Records in a Query Result Set Is Not Working Properly | No |
1 | 282 | SQL LIKE Operator Not Working Properly | No |
1 | 283 | ftSmallInt Field Type Incorrectly Referenced for C++Builder 3 | No |
1 | 284 | SQL ORDER BY Clause is Not Working Properly When Referencing Column Correlation Names | No |
1 | 285 | UPPER and LOWER Functions in SQL Causing Access Violations | No |
1 | 286 | Single-Field Aggregate Functions in SQL Columns with No GROUP BY Clause Causes an Error | No |
Build | # | Title | Workarounds |
None |
This web page was last updated on Wednesday, October 30, 2024 at 11:41 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |