You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
and on mysql it means the caller can't fold this into their own transaction
To be fair, there's not really any way to write `find_or_create` that isn't racy. Closest you can get (that works on both pg and mysql) is a select for update, followed by an insert ignore, followed by another select -- but even that can fail
I know that, but create_or_find is also racy, and its own docs say as much, so I'm confused about why it's been added if I wanted consistency I wouldn't use either of these APIs
I am definitely not advocating that `create_or_find` is a good API. I argued against adding it at the time. For real improvement to happen though, I think Rails needs to:
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
