Hi
It all nails down to selectivities then. In this particular case..some columns
have names CHARSET. No point.
But insert takes 0.5 seconds on a good hardware. That’s...rude.
But yeah, design is consistent. Agree on that
/Laimis N
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Stefan Koehler
Sent: Friday, February 19, 2016 4:29 PM
To: l.flatz@xxxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: Re: LOL: 122 one column indexes on 122 column table
Hi Lothar,
the 122 columns are extreme of course, but i just wanted to say that a lot of
single column indexes can make sense too. It is not always all for nothing.
Normally if you want index combine you would go for a bitmap index unless
there could be locking issues.
"l.flatz@xxxxxxxxxx" <l.flatz@xxxxxxxxxx> hat am 19. Februar 2016 um 14:32--
geschrieben:
Hi Stefan,
You have all 122 columns in different combinations searched? Hardly.
It is conceivable, but my experience tells me that most of the time it is
pure incompetence.
I have seen such a situation that you describe with the early
"pre-google" web searcher apps. Much more often people don't know that an
index can have more than one column.
Normally if you want index combine you would go for a bitmap index unless
there could be locking issues.
Regards
Lothar
