If I understand what they are saying / what the situation is, then
that seems like a reasonable limitation on using indexes for
optimization.
Chuck
On Oct 30, 2007, at 11:42 AM, John Huss wrote:
For example, the FrontBase mail list archive has this message:
Subject: [RESOLVED] Re: Optimization/Caching/Indexing how-to
The order of the columns in the composite index definition is very
important for your case.
If you want the optimal performance, you need to put the timestamp
column last in the index definition because it is used with a
range. The server cannot use the column of an index after one with
a range qualifier.
For example, in your case, if your composite index is define like
these example with a = check on fkY and fkZ and a range on dateX:
- (dateX, fkY, fkZ), only the date columsn is used like an index
(dateX)
- (fkY, dateX, fkZ), only the fkY and date columsn is used like an
index (fkY, dateX)
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
