Open JeremyThiesen opened 12 years ago
The fastest way to deal with this would be to migrate from the SQL API for fusion tables to the un-deprecated one. I'm not even sure which we are using, so maybe nothing is needed, but my point is we don't have to change databases (which would be hard):
https://developers.google.com/fusiontables/docs/v1/getting_started#migrate
That said, there may be other good reasons to consider a new stack, I know Justin has advocated for that, perhaps he could weigh in on why that is important, I will ask him by email.
Yes I did mention PostgreSQL with PostGIS bindings (PostGIS spatially enables PostgreSQL). It is the most robust spatial database available and outperforms proprietary competitors in both functionality and speed.
Google SQL API is deprecated and being discontinued at the end of the year, so we need to switch to a new database architecture. Justin had mentioned PostgreSQL I believe.