#sqlx
Live, measured metrics for the hashtag #sqlx from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #sqlx
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 · mas.to (Mastodon public tags API) · fetched 2026-07-27 07:05 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-07-27 07:05 UTCNo related tags with measured usage found for #sqlx.
Live pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-07-27 07:05 UTCEverything below is measured over the latest 40 public posts (spanning ~22408 hours).
Posting hours (UTC) — busiest: 20:00
Languages: English (35) · Russian (4) · Chinese (Taiwan) (1)
Avg boosts / post: 0.6
Top of the latest posts
I use #sqlx, and I wanted syntax highlighting for embedded #SQL queries in my #Rust code. Making that work in #Neovim led me to learning a few things about #Treesitter, and #NixOS packaging conventions. Here's my write-up! Public replies to
I really like using sqlx in rust. But wow I get many errors from rust-analyser when my database is offline. It always happens while doing some change, so I briefly think I've broken something mayor. #rustlang #sqlx
#SQL interfaces could use a way to conditionally enable statement rows. If one writes query by hand you enable or disable statements with just adding "--" at the beginning of the line SELECT * FROM example WHERE 1=1 AND a = ? AND b = ? -- A
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/sqlx