View Incident Report

Serious

Reported By: John Braga
Reported On: 4/12/2002
For: Version 3.08 Build 1

# 1086 Specifying Joins in Certain Order Can Cause AV During Query UnPrepare

I have encountered what I believe to be a bug in 3.08 (running local, not c/s). This query caused my Asta Dbisam server to crash, and when I run it in DBSYS it runs correctly the first time, then if I attempt to rerun the query it gives a "invalid filter on Rates table" message, and then abends when I try to close the query or terminate the program.

SELECT DISTINCT AE.BrnId, CL.ClId, CL.ClName, AE.AStartDate, BR.Quote,
 
 RA.RId, RA.RDesc,
 COUNT(AE.EmpId) as Worked
 
 FROM "alemp" AE, "bkemp" BE, "client" CL, "bref" BR, "rates" RA 
 WHERE AE.BkId=BE.BkId 
 AND BR.BrnId=BE.BrnId 
 AND CL.ClId=BR.ClId 
 AND CL.ClRate=RA.RId 
 AND AE.TmId <> NULL 
 AND AE.InvId IS NULL 
 AND AE.AStartDate >= "2002-03-11" 
 GROUP BY 1, 2, 3, 4, 5, 6, 7
 ORDER BY AE.AStartDate, CL.ClName

Comments

Problem was due to join ordering and improper order of the engine freeing join information.

Resolution

Fixed Problem on 4/13/2002 in version 3.09 build 1

More Support Options

Search Incident Reports

Support Forums

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals

Roadmap