I have to make a decision between MySQL and PostgreSQL which have to store POIs and let perform mostly - but not only - proximity queries (point(s) in polygon).
Let me ask it this way: Is there anyone who can report about MySQL (version 5.1 GIS?) and/or give reasons why (or why not yet) to use MySQL in a productive linux environment together with GeoServer?
Regards,
Stefan
Well, MySQL still doesn't have 'real' spatial operations, afaik. It's all still against the bounding envelopes. So I don't think it'll actually be accurate for proximity queries.
To account for this we do the real spatial operations in java, which means loading everything from the db in to java objects, which obviously doesn't perform real well. Theoretically we could do better if we used the mysql spatial operations to narrow things down, and then did the final filtering with java, but I don't believe we have that infrastructure, and it would take some non-trivial changes.
Chris
Stefan Keller wrote:
I have to make a decision between MySQL and PostgreSQL which have to store POIs and let perform mostly - but not only - proximity queries (point(s) in polygon).
Let me ask it this way: Is there anyone who can report about MySQL (version 5.1 GIS?) and/or give reasons why (or why *not* yet) to use MySQL in a productive linux environment together with GeoServer?
Regards,
Stefan
!DSPAM:4005,480fc46092354901796417!
------------------------------------------------------------------------
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone!DSPAM:4005,480fc46092354901796417!
------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel!DSPAM:4005,480fc46092354901796417!
Chris Holmes ha scritto:
Well, MySQL still doesn't have 'real' spatial operations, afaik. It's all still against the bounding envelopes. So I don't think it'll actually be accurate for proximity queries.
To account for this we do the real spatial operations in java, which means loading everything from the db in to java objects, which obviously doesn't perform real well. Theoretically we could do better if we used the mysql spatial operations to narrow things down, and then did the final filtering with java, but I don't believe we have that infrastructure, and it would take some non-trivial changes.
Yep, correct, at the moment we only encode BBOX filters in SQL whilst
all other spatial operations are performed purely in memory (so by loading everything from the DB).
Also CRS support is missing. For some other concern about mysql usage,
see my December mail about it:
http://www.nabble.com/MySql-5.1…-what-a-delusion…-td14556654.html
Cheers
Andrea