Icon View Incident Report

Serious Serious
Reported By: Paul Richardson [E.M.A Computer Solution
Reported On: 7/5/2019
For: Version 4.48 Build 4
# 4754 Executing SQL Joins on Date and TimeStamp Fields Can Cause an "Not a Valid Timestamp" Error

There is an error message when you are comparing a date field to a timestamp field in a join clause:

"DBISAM Engine Error #11279 An unknown error (''0.0' is not a valid timestamp') occurred witht he connection to the database server at 'IP ADDRESS', please check the server log.

select 
st_end_date,
jc_start
from Jobcycle 
left outer join staff a on ST_Inits = JC_AllocID and ((ST_End_Date is null) or (JC_Start < ST_End_Date)) 



Comments Comments
This bug was introduced as part of the fix for incident #4736.


Resolution Resolution
Fixed Problem on 7/16/2019 in version 4.48 build 5


Products Affected Products Affected
DBISAM Additional Software and Utilities
DBISAM ODBC Client-Server
DBISAM ODBC Client-Server with Source
DBISAM ODBC Standard
DBISAM ODBC Standard with Source
DBISAM ODBC Trial
DBISAM VCL Client-Server
DBISAM VCL Client-Server with Source
DBISAM VCL Standard
DBISAM VCL Standard with Source
DBISAM VCL Trial

Image