Greg Stark wrote:
Just as a bit of supporting anecdotal evidence. I ended up storing longitude
and latitude redundantly in my tables as a point and also as a 0-area box just
so I could use the box box operator because there's no
contains operator.
If necessary, I will add missing operators.
Tom Lane <[EMAIL PROTECTED]> writes:
> As an example, contains/contained in are pretty meaningless for two points;
> but it would be very useful to directly support queries like "point is
> contained in box?", "point is contained in circle?" on a point column.
Just as a bit of supporting anecdot
Tom Lane wrote:
I'm not sure that you want to think of this as a direct copy of "what
rtree would do". The set of interesting operators isn't really the same
for all these types ... which was hard or impossible to support in rtree
but is trivial in GIST. As an example, contains/contained in are
Tom Lane wrote:
> (The TODO item as written is pretty much a dead letter anyway: nobody
> is going to do any more work on rtree. It should probably read "add
> more gist index support for geometric data types".)
TODO updated.
--
Bruce Momjian| http://candle.pha.pa.us
Janko Richter <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> What changes have you got in mind exactly?
> At first, I would implement all RTREE supported operators in GIST.
> Then, the GIST implementation may be a full replacement/alternative for RTREE.
That's already done.
> Futhermore, I wou
Tom Lane wrote:
Janko Richter <[EMAIL PROTECTED]> writes:
Is currently anybody working on extending rtree_gist? I have seen, it is moved
to core now. I had a look at it and because I have some experience with PGSQL's
Gist API,
I would do the job.
What changes have you got in mind exactly?
Janko Richter wrote:
> Bruce Momjian wrote:
>
> >Janko Richter wrote:
> >
> >
> >>Is currently anybody working on extending rtree_gist? I have seen, it is
> >>moved
> >>to core now. I had a look at it and because I have some experience with
> >>PGSQL's Gist API,
> >>I would do the job.
> >>
Janko Richter <[EMAIL PROTECTED]> writes:
> Is currently anybody working on extending rtree_gist? I have seen, it is moved
> to core now. I had a look at it and because I have some experience with
> PGSQL's Gist API,
> I would do the job.
What changes have you got in mind exactly?
"Janko Richter" <[EMAIL PROTECTED]> writes:
> OK. If I start developing now, is there a chance to put it in 8.1 or is it
> better to do it for 8.2. I'm not sure about feature freezing of 8.1.
Feature freeze for 8.1 is on Monday.
regards, tom lane
-
Bruce Momjian wrote:
Janko Richter wrote:
Is currently anybody working on extending rtree_gist? I have seen, it is moved
to core now. I had a look at it and because I have some experience with PGSQL's
Gist API,
I would do the job.
I don't think anyone is working in improving it, no.
OK.
Janko Richter wrote:
> Is currently anybody working on extending rtree_gist? I have seen, it is moved
> to core now. I had a look at it and because I have some experience with
> PGSQL's Gist API,
> I would do the job.
I don't think anyone is working in improving it, no.
--
Bruce Momjian
Is currently anybody working on extending rtree_gist? I have seen, it is moved
to core now. I had a look at it and because I have some experience with PGSQL's
Gist API,
I would do the job.
Regards,
Janko Richter
---(end of broadcast)---
TI
12 matches
Mail list logo
