that's what I get for not testing but just reading the manual :)
remind me not to answer questions when I don't have a database
handy.
sounds like Dan's going to have to add a column.
--- Kirtikumar Deshpande [EMAIL PROTECTED] wrote:
Rahcel, Dan:
I played with such things a long time
First time I've seen this post. And from the fine Data Warehousing
manual:
here's an example of range partitioning. Note the to_date in the
values clause. I don't see why you couldn't use
to_date(date_column,'MONTH')
Rachel
CREATE TABLE sales
(s_productid NUMBER,
s_saledate DATE,
Dan,
Good question, but unless I'm misinterpreting the results, the answer is
no...
SQL show release
release 902000100
SQL create table test
2 (a date, b number, c number)
3 partition by list (to_char(a, 'MON'))
4 (partition pJAN values ('JAN')),
5
The only way I see is using a system-maintained ( through a before-insert
and if necessary before-update trigger ) field that is set to
to_char(date_column,'mm') and then range partition on that.
At 03:24 PM 1/14/2004, you wrote:
Pardon if this is a duplicate, but the original has not shown up
You are right. Partitioning can still make your job as a DBA easier.
You can purge data (assuming the purge key is the same as partition key)
by dropping partition, etc.
-Original Message-
Sent: Thursday, March 14, 2002 12:33 PM
To: Multiple recipients of list ORACLE-L
I am new to the
You're right about the performance - they (the ones before I got here) tried
to run the stats and use choose and the performance was terrible. Now it is
not an option to use CBO. One of my tasks is to set up an environment and
take it to CBO, but this is not the immediate priority.
-Original
