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
Correct. Right now the only ways you'd be affected are if you use something which was deprecated in 1.4, have a manual `FromSql` impl involving `Pg` or `Mysql`, reference `NonAggregate` directly in your code, or are exhaustively matching `mysql::MysqlType`.
If you're building an application, none of those should be the case. All of these only affect very low level libraries interacting with Diesel. The `FromSql` change is the only one likely to actually affect anyone. All of the changes I mentioned have fairly simple migrations
If you fix deprecations every version, 2.0 will be no harder than if it'd been 1.5. We're holding ourselves to the same standards. It's just a few changes that we can't do a deprecation cycle for. https://discourse.diesel.rs/c/diesel-2-0 has the concrete details
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
