Jeff Davis <pgsql(at)j-davis(dot)com> writes:
> Also, there's a good case for continuous ranges for types like NUMERIC,
> but still continuous ranges don't seem quite as important overall.
Well it seems to me that the prefix_range type is continuous, so I would
tend to disagree here :)
A prefix_range is currently written as e.g. '012[3-5]' but could be
worked out to be represented '0123-0125'. In any case here are some
example of values that are contained in the mentioned range:
You get the idea, I suppose. The main use case is telephony routing:
searching for a prefix in your operator table when you know the phone
number that's calling you.
So let's not forget about continuous ranges, because there's at least
one real-world case that needs them. Oh and it's based on text really,
not on numbers, so that could be the range 'abc-abe'.
I'm too tired to try to understand how your proposal fits with what
would be needed to cover prefix ranges tonight, but I wanted to share
the use case at least.
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
In response to
pgsql-hackers by date
|Next:||From: Dimitri Fontaine||Date: 2010-10-31 21:12:12|
|Subject: Re: Simplifying replication|
|Previous:||From: Alex Hunsaker||Date: 2010-10-31 20:40:49|
|Subject: Re: why does plperl cache functions using just a bool for is_trigger|