Hi!
I am not shure this depends on UNICODE. My databases are _UNICODE=NO.
See the two new ones I posted today ("BUG: KB Stack type Illegal." and "Same
BUG? Wrong evaluation of where-clause") Maybe it's somehow related, as these
also have to do with the existence of an index.----- Original Message ----- From: Grossmann, Gert To: 'Gerald Nowitzky' ; Becker, Holger ; SAPDB Sent: Friday, June 06, 2003 2:15 PM Subject: RE: Grouping / max() with Index Reproducible with UNICODE database. Let's have a look at this ugly bug ;-) Gert > -----Original Message----- > From: Gerald Nowitzky [mailto:[EMAIL PROTECTED] > Sent: Freitag, 6. Juni 2003 13:54 > To: Becker, Holger; SAPDB > Subject: Re: Grouping / max() with Index > > > Hi! > Sorry, I forgot to mention: It is 7.4.3.17 on W2K. > I tried with a second instance of 7.4.3.17 on a XP machine, > there the bug > also "works" :-) > The explain for the query without the index is: > ZIP TABLE SCAN 1 > RESULT IS COPIED , COSTVALUE IS 5 > > After generating the Index, the explain tells me: > DBA ZIP IDX_ZIP_CTRY INDEX SCAN > 1 > * > DBA RESULT IS COPIED , COSTVALUE > IS 3 > > If you need anything else, just tell me. I can offer to > contact one of the > instances on my machines via WAN, if you want. > > (Gerald) _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
