Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Incident Reports » New Incident Reports for 4.48 |
Build | # | Title | Workarounds |
1 | 4732 | LASTAUTOINC Function Not Working Correctly when Called from INSERT Statements | No |
2 | 4736 | JOIN Conditions with Mismatched Types Can Cause Incorrect Results | No |
2 | 4737 | Executing Parameterized Queries from a 4.48 Client to a 4.45 Database Server Can Cause an AV | No |
3 | 4752 | SQL SELECT JOINOPTIMIZECOSTS Keyword Not Working Properly | No |
4 | 4754 | Executing SQL Joins on Date and TimeStamp Fields Can Cause an "Not a Valid Timestamp" Error | No |
5 | 4756 | Upgrading Very Large Tables Can Fail Due to Range Issue with Offset Calculation for Text Indexes | No |
5 | 4757 | SELECT COUNT(*) Queries that Contain Sub-Queries in WHERE Clause Return Incorrect Result | No |
6 | 4764 | Mirroring Version of DBISAM Database Server Not Replicating Data Properly | No |
6 | 4765 | Queries that Trigger Progress Events on the Client Can AV if Progress Event Processes Messages | No |
7 | 4776 | Joins with Many Repeating Values and Un-Optimized Conditions Can Cause Incorrect Results | No |
7 | 4786 | CASTing BLOBs to VARCHARs Causes Incorrect Record Values in Result Set | 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 |