Geospatial indexing lets you query for points near a given point. But sometimes that's not enough. This short demo shows how to use geospatial queries to see which state or country a point is within.
From time to time, I get told that I write strange-looking
for loops. This goes back almost thirty years to some tricks I picked up at Oracle when I was working on the RDBMS kernel. The state of compilers was much more primitive then than it is now. C++ didn't exist, and there wasn't even an ANSI C standard yet.
How to cope with differing newline formats on different operating systems, and avoiding tabs in revision control.
In the past, Java forums have been peppered with complaints from C++ folks about the lack of destructors in Java; here are some examples I found from a simple Google search:
I've gotten involved in an activity which uses various social networks to promote itself. The organizers have a twitter account for the entity, and share control over a Facebook page and LinkedIn groups for it.
Managing this is painful. When I want to tweet about something from the activity-specific twitter account, I have to sign out of my twitter account, sign in to the other, send the tweet, sign back out, and sign back in to my personal account. Imagine doing that for three or more other applications.
Accessing data in a database depends on the data model implemented by that database. The data model affects the operations available and the API used by clients to operate on that data. Different data models may provide more or less raw functionality. Usually, the less functionality provided directly by the data model, the more the client application must do for itself.
There are a lot of buzzwords around databases these days: availability, scalability, single-master, dynamo, documents, key-value stores, etc.
Unfortunately, I haven't seen a good roundup of things to think about when choosing a data storage technology. There's certainly a lot of hype, and a lot of activity on blogs and the twittersphere.