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
In the past two weeks, I've spent quite a lot of time testing SQL/JSON path functionality of seven SQL databases. The reason was the upcomming PostgreSQL 12 release, which will introduce SQL/JSON path. THREAD
I created 230 test cases. It took me 16 footnotes, some of them quite long, to describe all the limitations I found. Here is the result in one picture. PostgreSQL still "red" and "n/a" because this picture is based on PostgreSQL 11. https://modern-sql.com/static/sm-blog-whats-new-in-sql2016.json-path.en.xRSTIPem.svg …
All implementations are utterly incomplete and some of them have interesting bugs and conformance issues (of which I reported some—those where I believe it makes sense). I wonder what spec they were working against.
An then there is PostgreSQL 12 (beta 3). There is only one missing feature (datetime) which is being worked on. The only conformance issue I found is also being worked on. That's it. Everything else if fine. The most complete and correct SQL/JSON path implementation I've seen.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
