Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Index compression vs. table compression

Re: Index compression vs. table compression

From: DA Morgan <damorgan_at_x.washington.edu>
Date: Sun, 23 Jan 2005 11:23:26 -0800
Message-ID: <41f3f9a0$1_1@127.0.0.1>


Thomas Kyte wrote:

> In article <cstu76$rra$1_at_news-02.connect.com.au>, Howard J. Rogers says...
>

>>Thomas Kyte wrote:
>>[snip]
>>
>>
>>>I think most people think of a single key lookup as "a lookup by key that
>>>returns a single row -- a lookup".
>>>Lookups are generally considered (in my experience) to return a single row.
>>
>>Not in mine.

>
>
>
> lets take a vote --

A typical lookup table of mine looks something like this:

SELECT city_name
FROM zip_city
WHERE zip_code = '98040';

Sure enough returns one and only one row.

And autotrace clearly shows that it uses the index.

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace 'x' with 'u' to respond)


----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= East/West-Coast Server Farms - Total Privacy via Encryption =---
Received on Sun Jan 23 2005 - 13:23:26 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US