#sqlindex
Live, measured metrics for the hashtag #sqlindex from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #sqlindex
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-28 00:17 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-28 00:17 UTCNo related tags with measured usage found for #sqlindex.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 00:17 UTCEverything below is measured over the latest 5 public posts (spanning ~1248 hours).
Posting hours (UTC)
Languages: English (5)
Avg boosts / post: 0
Top of the latest posts
Why does this SQL JSON extract never use the index? Why does this SQL JSON extract never use the index. The SQL code queries JSON with JSON_EXTRACT. In MySQL that cannot use a regular index. In SQL use a generated column with an index. #wha
What's wrong with this SQL LIKE forcing a full scan? What's wrong with this SQL LIKE forcing a full scan on a search. The SQL code uses LIKE with a leading wildcard. In MySQL that cannot use an index. In SQL one search scans millions of row
What's wrong with this SQL OR killing the index? What's wrong with this SQL OR killing the index on a search. The SQL code uses OR on two indexed columns. In MySQL OR often prevents index usage. In SQL APIs one OR turns a millisecond query
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/sqlindex