Re: artificial values vs null
- From: Connor McDonald <hamcdc@xxxxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Sat, 25 Sep 2004 04:55:04 +0100 (BST)
If the 'null' value needs to be selected, another option is creating an
appropriate function based
index. This is a sort of "have your cake and eat it" scenario - the column
value is null but it
can be located via an index.
Cheers
Connor
--- Richard Foote <richard.foote@xxxxxxxxxxx> wrote:
>
> ----- Original Message -----
> From: "Niall Litchfield" <niall.litchfield@xxxxxxxxx>
>
> > and use artificial values instead. This wasn't the focus of the
> > original discussion, which is why I've renamed the subject line, but
> > is an area where not using NULL when one should can seriously mess
> > with the optimizer.
>
>
=====
Connor McDonald
Co-author: "Mastering Oracle PL/SQL - Practical Solutions"
ISBN: 1590592174
web: http://www.oracledba.co.uk
web: http://www.oaktable.net
email: connor_mcdonald@xxxxxxxxx
Coming Soon! "Oracle Insight - Tales of the OakTable"
"GIVE a man a fish and he will eat for a day. But TEACH him how to fish,
and...he will sit in a boat and drink beer all day"
------------------------------------------------------------
___________________________________________________________ALL-NEW Yahoo!
Messenger - all new features - even more fun! http://uk.messenger.yahoo.com
--
//www.freelists.org/webpage/oracle-l
Other related posts:
