![]() ![]() For me PGSQL was the only one capable to do this reliable.įor true geospatial data models that correctly implement most geospatial predicates and operators your only practical option is PostGIS or Oracle Spatial. When you do that within a second, you got yourself a good database. ![]() ![]() No more then a thousand points of interest, lets say. Make a small application that will show a map, put 100 million points of interest on that map, that are contained in the table we talk about, and now as you scroll the map, select the middle of view as your circle and select on a small radius only those points of interest inside that radius. The only one was PostgreSQL.Īnd before starting to bash me, please do this. Not Maria, not Access, not Oracle, not NoSQL, not MSSQL, not MySQL - all of them failed. Out of my tries, my clients tries, and my friends tries, only one DB was up to this task. And when you have a table with 100 million rows in it, and an application is not loading data from that table to show it to its users in the same second, you already lost the battle. My clients wanted to have data in front of their eyes the same second when they clicked the button. Nothing else mattered, not license price, not whistles and bells, not hype. For most of the projects where the DB really mattered, throughout my 10+ freelancer carrier, it came down to one thing that client really cared about. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |