Hi, > We did look at allowing general functions for partitioning and this > was one concern. The other is that we want to enforce that a row > only gets inserted into a single partition, so we wanted a > declarative syntax where it was relatively easy to check that range > and list specifications don't overlap. >
Detection of mutually exclusive ranges might not turn out to be so easy afterall. I think there is some code in the constraint_exclusion area which might help out in this. Regards, Nikhils -- EnterpriseDB http://www.enterprisedb.com
