Is there any plan of allowing non-range partitioning of spatial indexes

Question

our application is really lacking the ability of spatial index being partitioned by list. We are binning information in our data warehouse by spatial locations, and when we query it (actually, MapViewer is generating a tile), entire geometry set is searched because table is list-partitioned and we cannot have local spatial index.

Answer 1

Hi,
I'm not in a position to answer the question about list partitioning, but would a pseudo-list partition implemented as a range partition work? For example, something like this:
CREATE TABLE customers (
  first_name    VARCHAR2(20),
  last_name     VARCHAR2(20),
  address_1     VARCHAR2(20),
  address_2     VARCHAR2(20),
  city          VARCHAR2(20),
  state_abrv    VARCHAR2(3),
  postal_code   VARCHAR2(10),
  customer_id   NUMBER NOT NULL UNIQUE)
  PARTITION BY RANGE (state_abrv) 
   PARTITION ALASKA         VALUES LESS THAN ('AKz'),
   PARTITION ALABAMA        VALUES LESS THAN ('ALz'),
   PARTITION ARKANSAS       VALUES LESS THAN ('ARz'),
   PARTITION AMERICANSAMOA  VALUES LESS THAN ('ASz'),
   PARTITION ARIZONA        VALUES LESS THAN ('AZz'),
   PARTITION CALIFORNIA     VALUES LESS THAN ('CAz'),
   PARTITION WYOMING        VALUES LESS THAN ('WYz')
   );I've used this method in the past, although I agree a list partitioning solution is much preferred.
Dan