Despite Microsoft's claims to the contrary, SQLServer doesn't have a
real spatial capability. Neither does MySQL. SDE/SQLServer does, but
SDE isn't cheap. PostgreSQL plus PostGIS (PostGIS is actually a patch
to the schema mechanism) yields a spatial database on a par with Oracle
and even acknowledged to be that good BY Oracle at times, usually when
Oracle has released an update to beat features in place already in
PostGIS. And did I mention that PostGIS hasn't been out of beta but a
couple of years and is still that good?
I think that, for most installs, we could have a PostgreSQL package that
could drop in and then a script that puts PostGIS on top, then import
the basic schemas.
I don't see it as more than a drop-in.
gerry
Jason Winningham wrote:
On Oct 4, 2007, at 7:03 PM, Tate Belden wrote:
Is that even possible? To standardize on a generic 'SQL' so a specific
set of features offered by any one SQL server don't dictate that
server and only that server can be used?
I seem to recall that postgres has some specific GIS-type extensions
(PostGIS?) that would be desirable for an xastir implementation.
<queue Gerry>
I wouldn't worry too much about portability issues - I would expect the
database engine to be at least as portable (if not more so) than the
rest of the xastir support packages.
-Jason
kg4wsv
_______________________________________________
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
--
Gerry Creager -- [EMAIL PROTECTED]
Texas Mesonet -- AATLT, Texas A&M University
Cell: 979.229.5301 Office: 979.458.4020 FAX: 979.862.3983
Office: 1700 Research Parkway Ste 160, TAMU, College Station, TX 77843
_______________________________________________
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
