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
Does any SQL database actually implement IEEE 754 for floats? MySQL can't represent NaN or Infinity, SQLite can't represent NaN (and has no way to specify Infinity as a literal, but will coerce 9e999), and PG returns true for `'NaN'::float = 'NaN'::float`
NaN being equal to itself in PG probably isn't a huge deal (though it is quite surprising). Not supporting NaN or Infinity at all seems more likely to cause issues, but even then it's still niche. But not implementing floating point types to spec seems like such a weird omission
MySQL's behavior here is especially weird. It absolutely implements IEEE 754 under the hood, including NaN not equaling itself. But you cannot insert NaN, Infinity, or -Infinity into a table, nor is there a literal form. So you can only observe this with bind params.
Google BigQuery implements IEEE-754 for all finite values and all operations where at least one input is non-finite. Not sure the use case here but could be worth a try 
No use case. Curiosity of an orm maintainer
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
