It does. The point is that the system is set up to limit the bad
consequences. You might (will) get wrong query answers, but the
heap data won't get corrupted.
Tom,
if this is our goal -
"can return wrong query answers, but should not corrupt the heap data." and if we make Thick indexes capable of that, can i consider that as a thumbs up from your side? As you may already know, this will only happen when there is a volatile function based index.
Heikki,
Please let me know, if you feel otherwise.
Thanks,
Gokul.
