live wire
▸Snowflake’s Cortex Agent quickstart routes metrics and transcripts with prompt rules—but documents no authorization boundarySnowflake▸Oracle Select AI generates SQL/PGQ for property graphs—but errors if one AI profile mixes graphs with tables or viewsOracle▸Domo’s data team standardizes MCP builds with shared scaffolding; beta toolkits inherit user permissionsDomo▸Databricks proposes five outcome signals for agentic BI—and says dashboard counts and license usage miss decision qualityDatabricks▸One vibe-coded database app needed 56+ human test hours and three repair rounds despite AI Studio’s verification claimsMancas & Mancas / arXiv▸BigQuery AI.IF’s default cost mode trains a local model for most rows—and drops row-error thresholdsGoogle Cloud▸AWS’s multi-tenant data-agent pattern gives the broker Lambda no data permissions; Cognito roles carry Lake Formation scopeAWS Big Data Blog▸Amazon OpenSearch’s optimized engine adds nested agent traces, but AWS reserves it for log analytics—not vector searchAWS▸Two interpretation-based provenance semantics cannot express SQL bag difference, new theorem showsKolaitis / arXiv▸Databricks Feature Views reuse one definition for training and live scoring, but online lookup still returns latest available stateDatabricks▸Databricks Genie’s Slack and Teams previews default channel answers to public, even when viewers lack source-data accessDatabricks▸Snowflake’s two-tool GraphRAG agent beat a seven-tool graph setup 70% to 60% on 22 ontology questionsSnowflake Engineering▸Semantix opens an Apache-2.0 semantic-first data-agent stack, but labels the project WIP and has no release or adoption yetGitHub / icosmos-space▸Confluent defines Streamhouse as shared current state for agents and apps, but says broader semantics and governance are still to comeConfluent▸Snowflake’s Cortex Agent quickstart routes metrics and transcripts with prompt rules—but documents no authorization boundarySnowflake▸Oracle Select AI generates SQL/PGQ for property graphs—but errors if one AI profile mixes graphs with tables or viewsOracle▸Domo’s data team standardizes MCP builds with shared scaffolding; beta toolkits inherit user permissionsDomo▸Databricks proposes five outcome signals for agentic BI—and says dashboard counts and license usage miss decision qualityDatabricks▸One vibe-coded database app needed 56+ human test hours and three repair rounds despite AI Studio’s verification claimsMancas & Mancas / arXiv▸BigQuery AI.IF’s default cost mode trains a local model for most rows—and drops row-error thresholdsGoogle Cloud▸AWS’s multi-tenant data-agent pattern gives the broker Lambda no data permissions; Cognito roles carry Lake Formation scopeAWS Big Data Blog▸Amazon OpenSearch’s optimized engine adds nested agent traces, but AWS reserves it for log analytics—not vector searchAWS▸Two interpretation-based provenance semantics cannot express SQL bag difference, new theorem showsKolaitis / arXiv▸Databricks Feature Views reuse one definition for training and live scoring, but online lookup still returns latest available stateDatabricks▸Databricks Genie’s Slack and Teams previews default channel answers to public, even when viewers lack source-data accessDatabricks▸Snowflake’s two-tool GraphRAG agent beat a seven-tool graph setup 70% to 60% on 22 ontology questionsSnowflake Engineering▸Semantix opens an Apache-2.0 semantic-first data-agent stack, but labels the project WIP and has no release or adoption yetGitHub / icosmos-space▸Confluent defines Streamhouse as shared current state for agents and apps, but says broader semantics and governance are still to comeConfluent
nl2sql.ai
releaseRelease

Wren fixed DISTINCT ON twice—Python deployments need the second release

The semantic-core patch landed first; the Python binding followed 46 minutes later. Pin and test the package your application actually loads.

By The News Desk· Oct 23, 2026the quick take — two AI hosts go live when you do

WrenAI’s October 23 fix for DISTINCT ON arrived in two package releases, not one. The project published wren-semantic-core 0.5.1 at 08:26 UTC with a planner change that collects DISTINCT ON columns when building model plans. It then published wren-core-py 0.8.2 at 09:12 UTC specifically to carry that fix into the Python bindings. Wren semantic-core release Wren core Python release

That sequence matters operationally. A deployment that consumes the Python binding does not get the binding update merely because the lower-level semantic-core tag exists; Wren’s own 0.8.2 release note describes the package as shipping the 0.5.1 fix in the bindings. Teams should therefore verify the version resolved by the application environment, rather than treating the first repository notification as proof that the running path changed. Wren core Python release

What to test

The narrow regression target is a query whose plan depends on PostgreSQL-style DISTINCT ON columns. Before rollout, capture the generated SQL and the returned rows from a representative query; after upgrading the Python package, repeat both checks. A successful query is not enough evidence if it selects a different row per group or changes ordering-dependent output. The semantic-core release identifies model-plan column collection as the corrected behavior, while the binding release identifies the package that exposes it to Python consumers. Wren semantic-core release Wren core Python release

Wren’s 0.5.1 semantic-core release also preserves SQL literals while resolving derived cube measures, but the Python 0.8.2 note names only the DISTINCT ON fix. Operators should not infer from the binding note that every semantic-core change was bundled unless their resolved dependency graph or a direct regression test demonstrates it. Wren semantic-core release Wren core Python release

The practical lesson is package-specific: record the exact Wren component and version in test evidence. In a multi-package repository, “fixed upstream” and “available in the runtime binding” can be separate release events.

sources

Filed by The News Desk. Corrections: desk@nl2sql.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.

    more from the desk