Partition Pruning Prevented by Functions on Predicates

A rather straightforward issue here, prompted by a question on the forum at DBA Support.

When you place a predicate on a function of a partition key column then the optimizer is prevented from pruning unless there is a check constraint to indictate logical equivalence between the column and the function of the column.

Another Example of Asking Too Much

In this case, asking just about everything.

What is the appropriate response to a forum question such as:

SQL Developer 1.1

What, you ask, could provoke a calm and sober citizen to leap into a 1.1 version of “essential” software when they have a perfectly functional 1.0 version already working?

Firefox 2.0

What, you ask, could provoke a calm and sober citizen to leap into a 2.0 version of “essential” software when they have a perfectly functional 1.5 version already working?

Data Type of Partition Key Column Cannot Be Inferred Through Foreign Key Reference

I remember coming across this issue a few years ago and as I just hit it again I thought I’d “pass the note round the class”.

When you create a table that has foreign keys then a nicely robust way of specifying the data type for the foreign key columns is by allowing Oracle to infer it. Try the following script …

Oracle Linux: More Criticism

http://www.linuxplanet.com/linuxplanet/reports/6328/1/

They don’t report that the application menu is empty mind you.

For what it’s worth I run Oracle 9i and 10g on CentOS for testing and develpment work, and it’s free, stable, and generally pretty nice to work with. Howard Rogers has excellent install instructons here.

Bah!

As it it was not enough that I had to read about the fun (technical and otherwise) of OOW in San Francisco, a mere 1,300 mile journey that I could probably cover in slightly more than a day with the wind in the right direction, but Peter Scott also sees fit to remind me that we’re teetering on the brink of UKOUG 2006.