Raimund Jacob wrote: > i want to tweak my tables a little and want to know how much of my > character-columns are actually used. so, i do > > select max(length(some-character-column)) from table > > ...which works fine for some tables and columns. however, > there is one > fairly large table (2.7 million rows) where this fails: the length is > always 3. min and max values are 3. (the entries have > different sizes, > though) the EXPLAIN statement tells me that an index scan was made on > this column (there is an index). > question: is this a known ...umh... feature regarding length > of indexed > columns? is there another way to acquire these information? would > dropping the index force the kernel to scan the actual data > and deliver > correct information? i dont care for the time it takes...
This sounds like a unknown bug. Could you please provide more information especially the table and index definition and the output of the explain statement. Dropping or disableing (alter index <idxname> on <tabname> disable) the index should be a workaround. Best regards, Holger SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
