Re: box function implemented?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: wsheldah(at)lexmark(dot)com
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: box function implemented?
Date: 2003-05-01 00:53:45
Message-ID: 25556.1051750425@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

wsheldah(at)lexmark(dot)com writes:
> I think I found a glitch either in the box function or in the docs for
> postgresql 7.3.2. The online docs say that the box function can find the
> intersection box between two boxes.

Looks like it should be referring to box_intersect(). Will fix the docs
--- thanks for catching this!

> Having said all that, I have to say that postgresql's geometry functions
> are fantastic. I just came up with my first need for them, and it looks
> like they're going to really save me from writing a chunk of code and speed
> things up. Thanks!

FWIW, I don't have a whole lot of confidence in the built-in geometric
functions. They started as an academic exercise (like the rest of
Postgres) but have not been wrung out the way the rest of the system
has. It seems like everyone who uses them finds more bugs. So use 'em,
by all means, but test before you trust.

You might also care to look at PostGIS, which has the intention of being
industrial-strength code. I'm not sure what their level of wrung-out-ness
really is at the moment, but at least there are people actively working
on that code.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2003-05-01 01:15:40 Re: Problem with || and data types
Previous Message Tom Lane 2003-05-01 00:03:44 Re: dump/restore to 7.4devel giving "[archiver (db)] error returned by PQputline"