Run more than one query at a time
A long-running query used to freeze the whole app. Not anymore. Starting in v1.0.11, SnoutData runs your queries concurrently: fire off the slow one, open a new tab, and keep working.
You know the moment. You kick off a report that takes 40 seconds, and then you just wait. You can't check that other table, can't run a quick count, can't do anything until it finishes. That is exactly the moment we set out to fix.
Under the hood, every database connection has always been backed by a small pool of connections. The app just never let you use it. Now it does, and we gave you three things to go with it.
Real concurrency
Queries no longer block each other. Run a migration in one tab, a SELECT in another, and watch a dashboard in a third. The slow query in tab one never holds the others hostage, and every running tab shows a spinner so you always know what is still in flight.
Tune the pool to your workload
A new Connection pool size setting (per connection, 4 to 16) lets power users run more queries in parallel, which matters most when you are driving busy live dashboards. The default of 4 is right for almost everyone, and your database server's own connection limit still applies.
Your query is always first in line
Background work like live schema refresh and dashboard polling now runs on reserved connections, so it can never eat the whole pool and make your query wait. You stay in the fast lane.
A small change in how it feels, a big change in how it flows. Available now in v1.0.11: update from inside the app, or grab the latest at the download page.