sadpandajoeandClaude Sonnet 5
e9cef69d90
The previous commit's refresh(query, attribute_names=["status"]) correctly
avoids writing a dirty `status` itself (SQLAlchemy expires the named
attribute before reloading it, so a stale local value is discarded rather
than flushed) -- but verified empirically (SQLAlchemy 2.0.52) that the
reload's own SELECT still triggers a normal autoflush of any OTHER dirty
attribute on the object first. With a second field (e.g. tmp_table_name)
also dirty alongside status -- which is the normal, expected state when an
exception interrupts execute_sql_statements() partway through -- the
targeted refresh still emitted `UPDATE ... SET tmp_table_name=?` before
`SELECT ... status`. So the previous commit's comment claim ("without
writing this handler's own possibly-stale local state first") was only
actually true for the status column itself, not for pending local state in
general.
Wrapped the targeted refresh in `db.session.no_autoflush`: verified this
emits only the targeted SELECT, with no UPDATE beforehand, and leaves other
pending attributes exactly as dirty as they were, to be flushed normally by
this function's own commit() later (once past the STOPPED check). Updated
the comment to describe what's actually guaranteed now.
Added a direct regression test that captures the real SQL statements
handle_query_error() emits (via a SQLAlchemy `before_cursor_execute` event
listener, not mocked) with a second dirty field alongside status, and
asserts no UPDATE/INSERT appears before the targeted, single-column status
SELECT -- following the same verification method used to find the bug in
the first place, rather than only checking the final outcome (which this
bug doesn't actually corrupt, since the premature write happens inside a
transaction that gets rolled back on the STOPPED early-return path; the SQL
ordering itself is the only place this regression is observable). Also
extended the existing concurrency test with a second dirty field for the
same reason.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Superset
A modern, enterprise-ready business intelligence web application.
Documentation
- User Guide — For analysts and business users. Explore data, build charts, create dashboards, and connect databases.
- Administrator Guide — Install, configure, and operate Superset. Covers security, scaling, and database drivers.
- Developer Guide — Contribute to Superset or build on its REST API and extension framework.
Why Superset? | Supported Databases | Release Notes | Get Involved | Resources | Organizations Using Superset
Why Superset?
Superset is a modern data exploration and data visualization platform. Superset can replace or augment proprietary business intelligence tools for many teams. Superset integrates well with a variety of data sources.
Superset provides:
- A no-code interface for building charts quickly
- A powerful, web-based SQL Editor for advanced querying
- A lightweight semantic layer for quickly defining custom dimensions and metrics
- Out of the box support for nearly any SQL database or data engine
- A wide array of beautiful visualizations to showcase your data, ranging from simple bar charts to geospatial visualizations
- Lightweight, configurable caching layer to help ease database load
- Highly extensible security roles and authentication options
- An API for programmatic customization
- A cloud-native architecture designed from the ground up for scale
Screenshots & Gifs
Video Overview
Large Gallery of Visualizations
Craft Beautiful, Dynamic Dashboards
No-Code Chart Builder
Powerful SQL Editor
Supported Databases
Superset can query data from any SQL-speaking datastore or data engine (Presto, Trino, Athena, and more) that has a Python DB-API driver and a SQLAlchemy dialect.
Here are some of the major database solutions that are supported:
A more comprehensive list of supported databases along with the configuration instructions can be found here.
Want to add support for your datastore or data engine? Read more here about the technical requirements.
Installation and Configuration
Try out Superset's quickstart guide or learn about the options for production deployments.
Get Involved
- Ask and answer questions on StackOverflow using the apache-superset tag
- Join our community's Slack and please read our Slack Community Guidelines
- Join our dev@superset.apache.org Mailing list. To join, simply send an email to dev-subscribe@superset.apache.org
- Follow us on social media: X | LinkedIn | Bluesky | Reddit
- If you want to help troubleshoot GitHub Issues involving the numerous database drivers that Superset supports, please consider adding your name and the databases you have access to on the Superset Database Familiarity Rolodex
- Join Superset's Town Hall and Operational Model recurring meetings. Meeting info is available on the Superset Community Calendar
Contributor Guide
Interested in contributing? Check out our Developer Guide to find resources around contributing along with a detailed guide on how to set up a development environment.
Resources
- Superset "In the Wild" - see who's using Superset, and add your organization to the list!
- Feature Flags - the status of Superset's Feature Flags.
- Standard Roles - How RBAC permissions map to roles.
- Superset Wiki - Tons of additional community resources: best practices, community content and other information.
- Superset SIPs - The status of Superset's SIPs (Superset Improvement Proposals) for both consensus and implementation status.
Understanding the Superset Points of View
-
Getting Started with Superset
-
Deploying Superset
-
Recordings of Past Superset Community Events
-
Visualizations
