[postgis-devel] Spatial DB in a Box - Postgresql Bindings

[Craig Miller]

Thanks David.  I appreciate the response.

I did a little more searching with google.  It looks like GCJ works under
mingw now too.

http://www.mingw.org/download.shtml


--Craig


-----Original Message-----
From: postgis-devel-bounces at postgis.refractions.net
[mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of
dblasby at openplans.org
Sent: Friday, February 18, 2005 1:06 PM
To: postgis-devel at postgis.refractions.net
Subject: RE: [postgis-devel] Spatial DB in a Box - Postgresql Bindings

>>Will the use of GJC prevent a Windows version?

I think GCJ supports all the major platforms:

1. linux x86
2. windows x86 (might be using cygwin, not sure - waiting for someone to
try)
3. solaris sparc
4. Mac OS X, powerpc

GCJ is part of the GCC compiler.  I believe they can compile eclipse in
all those platforms (eclipse is MUCH more complex than JTS).  They may
have some SWT (thats a native-code GUI package) problems on OSX, but
thats not going to affect JTS.

The GCJ development list is very active.


>>Is GEOS being dropped due to performance?

GEOS has its own "market" and advantages.

The biggest advantage of the compiled JTS is that JTS is being actively
developed.  There's a ton of new stuff thats been/being added!  Check
out all the changes for 1.6 and the upcomming 1.7 version.

Also, there's lots of JTS-based java code (like the Polygonize example
in the [Add A function] section).  This functionality is trival to add.

I thought GEOS would have been faster than the compiled JTS - the
performance boost is an unexpected plus.

>Will adding support for multiple databases ultimately result in an
average
>product that supports a lot of databases rather than a single optimized
>product for a specific database (PostgreSQL)?

I dont think so - I see the main core of each database being backed by
JTS.  This is where all the actual processing occurs.

Each database will have its own "extras".  For example, the postgresql
version will have its own indexing and statistics (see the "To Do" at
the bottom of DB specific pages).

But, you are correct - there are some functions that could possibly run
slower in "Spatial DB in a Box" because it would not be able to
optimize.  I would expect these to be very small compared to the cost
of pulling a page off the disk.

dave






----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/
_______________________________________________
postgis-devel mailing list
postgis-devel at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-devel