A discussion came up today of why some location calculations where always off by 40% for geolocation.
Basically, we were converting it incorrectly; however, more interestingly is a page about geolocation and SQL. Things that developers often take for granted is the problem of database-side sorting.
Outside of Geolocation, "infinite scrolling" on web pages just makes me wonder how the SQL is handled. What if a record gets inserted between the scroll calls? How does one keep track. If you search online, there are many resources of how to scroll infinitely using jQuery and browser-side calls, but I'm sure there's one genius that has designed how the database handles the actual creation of the data.
No comments:
Post a Comment