SELECT "ldto"."Wsn"
   , "ldto"."Lsn"      
   ,"iq"."Id"      
   ,(SELECT COALESCE("Locked", 0)        
      FROM   "DataLock" AS "dl"        
      WHERE  "dl"."Id" = "ldto"."Lsn"          
      AND ("dl"."Wsn" = "ldto"."Wsn"           
      OR  "dl"."Wsn" = -1)) AS "Locked"        
   ,"ldto"."Units"
   ,"ldto"."NumPts"
   ,"ldto"."Start"        
   ,"ldto"."Stop"
   ,"ldto"."Step"
   ,"ldto"."NullVal"
   ,"ldto"."MinVal"
   ,"ldto"."MaxVal"        
   ,"ldto"."Flags"
   ,COALESCE("ldto"."LasId", 0) AS "LasId"
   ,"ldto"."Mean"
   ,"ldto"."StdDev"  
FROM (SELECT "ldti"."Wsn"              
         ,"alci"."Id"              
         ,MIN("alci"."Seq") AS "MinSeq"        
      FROM "LogData" AS "ldti"        
      INNER JOIN "AliasLogCurve" AS "alci"          
         ON "ldti"."Lsn" = "alci"."Alias"         
         AND "alci"."Id" IN (323)        
      GROUP BY "ldti"."Wsn", "alci"."Id") AS iq
INNER JOIN "AliasLogCurve" AS "alco"    
   ON "iq"."Id" = "alco"."Id"   
   AND "iq"."MinSeq" = "alco"."Seq"  
INNER JOIN "LogData" AS "ldto"    
   ON "alco"."Alias" = "ldto"."Lsn"   
   AND "iq"."Wsn" = "ldto"."Wsn"  
ORDER BY "Wsn"

---

 Comments and Workarounds

---

The issue was with how the query optimizer was using the dependency information for the joins. It was allowing the joins to be re-ordered in a way that broke the dependencies and caused incorrect results. The workaround was to add the NOJOINOPTIMIZE clause to the end of the query.

---

 Resolution

---

Fixed Problem on 3/10/2015 in version 2.18 build 4

---

 Products Affected

---

ElevateDB Additional Software and Utilities
ElevateDB DAC Client-Server
ElevateDB DAC Client-Server with Source
ElevateDB DAC Standard
ElevateDB DAC Standard with Source
ElevateDB DAC Trial
ElevateDB LCL Standard with Source
ElevateDB PHP Standard
ElevateDB PHP Standard with Source
ElevateDB PHP Trial
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial