I've been asked to create an index which combines two fields, date & location.
For reasons I don't really want to explain, we need/desire this index to
be in the order of date, location. The minor gotcha is that while location
will be populated at the time the record is created, the date field is not
updated until a later point in time. This date is a document print date.
So this date field will be going from a NULL value to a non-null value.
I recognize that this can result in record chaining in the data table.
In thinking about this, I realized this could have a similar affect
within the index. However, I've never read anything about index chaining.
Do/can indexes chain?
Should I be concerned about this?
--
Charlie Mengler Maintenance Warehouse
[EMAIL PROTECTED] 10641 Scripps Summit Ct.
858-831-2229 .NET? Not yet! San Diego, CA 92131
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Charlie Mengler
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
