There's also an error in the document (which is not surprising, since
the MySQL documentation on spatial is a little misleading, with most
all of the OGC functions documented when only the constructors and
accessors are actually fully implemented) which indicates that MySQL
supports:
Buffer(g,d)
ConvexHull(g)
Difference(g1,g2)
Intersection(g1,g2)
SymDifference(g1,g2)
Union(g1,g2)
When it actually does not.
P.
On 26-Dec-05, at 7:16 PM, Gregory S. Williamson wrote:
This seems to cover most of the major issues, although I'd point
out that the speed difference between the two is mostly obvious
when running single (or only a few) connections to the database; if
you need something that can support dozens / scores (or more) of
simultaneous connections the speed difference is markedly less, and
sometimes is reversed with Postgres showing an advantage.
Greg Williamson
DBA
GlobeXplorer LLC.
-----Original Message-----
From: UMN MapServer Users List on behalf of Shoaib Burq
Sent: Mon 12/26/2005 5:46 PM
To: [email protected]
Cc:
Subject: Re: [UMN_MAPSERVER-USERS] mysql?
Last year I was ask by my manager to compare the spatial capabilities
of Postgres and mysql.
See attached the report I gave him... it was a 1 hour job. so no
guarantees
regards
shoaib
!DSPAM:43b09cfe17901804284693!
