Flemming Frandsen wrote.... > I've tried getting an explaination from the database, and it has this > moronic idea that it would be cool to sort first when the index is on, > that would be stupid to begin with, but blowing up is worse: > > /opt/sapdb/indep_prog/bin/dbmcli on ZDB>sql_execute explain SELECT * > FROM "ticket" WHERE 1 IN (owner_dude_id, seater_dude_id, user_dude_id) > ORDER BY ticket_type_id > OK > > --- > /opt/sapdb/indep_prog/bin/dbmcli on ZDB>sql_execute select * from show > OK > END > 'TEST';'ticket';'TICKET_TYPE_ID';''ORDER BY' VIA INDEXED > COLUMN';' 40';'';'';'';'*' > 'TEST';'';'';' RESULT IS NOT COPIED , COSTVALUE IS';' > 61';'';'';'';''
......... Hey, keep cool, perhaps take a breath of fresh air outside your office. To use the word MORONIC is not the way we should talk with each other. And if I follow your argument (just checking the explain result), no selection of rows would be done, just sorting for fun. That would be really ..... (stupid or something like this). But we just walk along the index and check for this search condition. We do not sort first, store the sorted result and then start to check. Did you think this???? WE do NOT store the result if you see this explain-result The only opportunity we had if the index was not avalaible is to scan the whole table, check the search condition and store the result rows to be able to sort them. And if you only fetch the first x rows, much work was done just for nothing. What do you think (after some fresh air / a cup of coffee) about the database? Elke SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
