 |  LoginProducts  SalesSupportDownloadsAbout |
| Home » Technical Support » DBISAM Technical Support » Incident Reports » New Incident Reports for 4.04 |
New Incident Reports for 4.04The following is a list of the new incidents reported for version 4.04. Click on the incident # in order to view the details of the incident report.
Serious Problems
Minor Problems
Serious Problems
| Build | # | Title | Workarounds |
| 1 | 1579 | The OSWaitForEvent in the DBISAMLB Unit for Kylix Contains Invalid Code and Cannot Be Compiled | Yes |
| 1 | 1580 | SELECT COUNT(*) Returning an Empty Result Set Under Linux | No |
| 1 | 1581 | GROUP BY SELECT Statements Without an ORDER BY Cause Memory Leak | No |
| 1 | 1592 | Using Optimistic Locking Protocol Can Cause Unlock Errors When Changing Records with Active Filter | Yes |
| 1 | 1597 | Server-Side Procedures and Users Are Not Being Saved When Added to the Server Configuration | No |
| 1 | 1598 | MaxRowCount Property Set to 1 Causes 0 Rows to Show Up in the Result Set | Yes |
| 1 | 1603 | TDBISAMTable CreateTable Method Not Creating Full Text Indexes on Specified Fields | No |
| 1 | 1604 | RemoteLoginDialogProc Being Called Even Though It Is Not Assigned and Causing an AV | Yes |
| 1 | 1605 | Locate Randomly Not Finding the Correct Record | No |
| 1 | 1606 | The .SO Shared Object Libraries Are Missing for the Kylix Design-Time and Run-Time Packages | Yes |
| 1 | 1608 | Locate Not Working Properly with Filter and Certain Active Indexes Set | No |
| 1 | 1609 | Invalid Requests to the Database Server Result in an #15002 Error Uncompressing Data Exception | Yes |
| 1 | 1610 | TDBISAMDatabase BackupInfo Method Not Working Properly for Remote Sessions | Yes |
| 1 | 1611 | Altering a Table and Changing an Integer Field to an AutoInc Field Does Not Modify the Last Autoinc | Yes |
| 1 | 1615 | Altering an In-Memory Table Causes an Unknown Operating System Error | No |
| 1 | 1616 | Modifying a BLOB Field Using a TDBISAMBlobStream Component Does Not Work Properly | No |
| 1 | 1617 | Executing an SQL SELECT Query That Modifies the Index Position Can Cause a Hanging Read Lock | No |
| 1 | 1618 | Executing Queries Inside of Custom Functions Can Result in Random AVs | No |
| 1 | 1626 | Using a Constant Expression in an SQL JOIN Condition Causes an AV | Yes |
| 1 | 1635 | Random Concurrent Updates Mixed with Reads Can Cause AV During Searches and Reads | No |
| 1 | 1594 | Encryption and MD5 Hash Code Can Possibly Cause a Lockup on an AMD Machine Due to Integer Overflows | No |
Minor Problems
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 |
