Alexey Gaidukov wrote: > MaxDB 7.6.00.27 > > The testcase > > gis.invest is a table with millions records. The field COUNTER is the > PRIMARY KEY > > > > create table temp.test ( > id integer > ) > // > explain > select * from gis.invest,temp.test where counter=id > for reuse > > > TEMP TEST TABLE SCAN > 0 > GIS INVEST COUNTER JOIN VIA KEY COLUMN > 69584 > NO TEMPORARY RESULTS CREATED > RESULT IS COPIED , COSTVALUE IS > > 2 E10 > > > > insert into temp.test values(1) > // > explain > select * from gis.invest,temp.test where counter=id > for reuse > > > TEMP TEST TABLE SCAN > 0 > GIS INVEST COUNTER JOIN VIA KEY COLUMN > 69584 > NO TEMPORARY RESULTS CREATED > RESULT IS COPIED , COSTVALUE IS > 2 > > Hi,
it's definitive a bug and based on some type mixing within the join optimizer. I'll fix it with one of the next release (for detailed version info see http://www.sapdb.org/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1141684) As far as I can see this bug influences only the explain output not the decision of the optimizer so it should not be critical for your application. Thank you for reporting it. Kind regards Holger -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
