Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Incident Reports » Incident Reports Addressed in 3.13 |
Build | # | Title | Workarounds |
1 | 1112 | Executing a Joined SQL UPDATE Statement that Updates a BLOB Field Causes #8708 Record Changed Error | No |
1 | 1156 | Single Row Aggregate SQL Statements with Joins Results in Improper Results | Yes |
1 | 1163 | Multiple Quotes Embedded in SQL or Filter Expressions Not Being Resolved Properly | No |
1 | 1164 | Error #8711 DBISAM_ENDOFBLOB Returned When Executing TEXTSEARCH SQL Query on Server | No |
1 | 1165 | Using Explicit SQL SELECT Columns Followed By All Columns (*) Causes Incorrect Fields in Result Set | No |
1 | 1166 | SQL SELECT Statement STOP WORDS Clause Parsing Extra Token Incorrectly | No |
1 | 1167 | Executing an SQL UPDATE Statement Can Cause a #10249 DBISAM_LOCKTIMEOUT Error | Yes |
1 | 1168 | Executing an SQL SELECT Query Containing a Sub-Select Causes an #15002 DBISAM_UNCOMPRESS Error | No |
1 | 1169 | Using WriteHeaders=True Parameter for ExportTable Method Causes First Record to Be Overwritten | No |
1 | 1170 | Forcing Corruption on a Table for Testing Purposes Causes RepairTable/VerifyTable to Fail | No |
1 | 1171 | Executing a Live Query with a Constant Expression in the WHERE Clause Returns Incorrect Results | No |
1 | 1172 | SQL Statements Not Allowing the Use of the Dollar Sign ($) in Column Names | No |
1 | 1173 | Using CopyOnAppend to Add Record with BLOB Fields and then Using Plain Append Causes BLOB Corruption | 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 |