Note that foriegn key constraints are not compatible with MyISAM, which is the only MySQL database engine which supports spatial indexes. (MySQL is a well tested database for years and most of my data is relational, so I was planning to use MySQL or Microsoft SQL Server) Almost every time MySQL is mentioned on that page, it is to describe a feature that it does not support, but that Postgres does. However, there is a long list of features which Postgres supports and MySQL doesn't. It's not that MySQL doesn't support spatial data. The reason why they suggest using Postgres is that it has better support for spatial data. Would there be any processing disadvantages in context to algorithms used to compute nearby businesses if I choose to go with MySQL, how would it make my system slow? ( MySQL is a well tested database for years and most of my data is relational, so I was planning to use MySQL or Microsoft SQL Server) I was wondering what are the specific advantages of using PostgreSQL over MySQL in context to computing and fetching the location related fields. Customers can find nearby businesses around him.Both customer and business will have their locations stored.This is not how database is, only for rough idea or project.Here a user can register as a customer as well as a business ( customer's and business's name/address etc (all) fields will be separate, even if its the same user) There are multiple Tutorials/Questions over the Internet/Youtube/StackOverflow for finding nearyby businesses, given a location, for example ( Question on StackOverflow) :īut one thing common in these all is that they all prefers PostgreSQL (instead of MySQL) for Django's Geodjango library
0 Comments
Leave a Reply. |