live wire
▸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▸Graph-repair retrieval cut F1 by 0.126 on one suite; a learned router used fewer tokens than always-on retrieval in all sixLin et al. / arXiv▸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▸Graph-repair retrieval cut F1 by 0.126 on one suite; a learned router used fewer tokens than always-on retrieval in all sixLin et al. / arXiv
nl2sql.ai
guideOPERATIONS

Chat2DB can resume a failed import—but recovery policy still belongs to the operator

Version 5.3.9 beta 2 adds checkpoints, rejected-row exports and clearer counters. The useful change is not “retry”; it is making partial success inspectable.

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

Chat2DB’s latest beta turns bulk import from a one-shot dialog into a recoverable workflow. Version 5.3.9 beta 2 can resume failed or cancelled CSV, Excel and JSON imports from saved progress, groups continuation attempts in its task center, and keeps logs for each run. That reduces the cost of interruption, but it does not remove the need to decide what counts as an acceptable partial load. Chat2DB release notes

The important choice is stop versus skip

The release adds two policies for invalid rows: stop the import or skip the row. It also lets an operator download rejected rows for review. For supported databases, duplicate-key rows may be ignored as well. Those options describe different data contracts, not merely different user-interface preferences. Stopping protects an all-or-nothing expectation; skipping prioritizes throughput but produces a dataset that is incomplete until the rejected-row file has been reconciled. Chat2DB release notes

The new counters make that distinction visible. Import progress now separates rows processed, stored and rejected, while SQL import logs show each batch’s statements, statement count and known affected rows. The notes explicitly say some statements may have unavailable row counts. Teams should therefore avoid treating “task completed” as proof that every input record landed; stored and rejected counts are the more useful completion evidence. Chat2DB release notes

Resume does not mean replay is harmless

The release notes say an interrupted import can continue from saved progress, but they do not specify transaction boundaries, checkpoint granularity or whether resumed writes are idempotent across every supported database. That absence matters when a task is cancelled after the database has accepted rows but before the client records its checkpoint. Until the project documents those semantics, operators should test a representative interrupted run against a disposable table and verify row counts and duplicate behavior before using resume on production data. Chat2DB release notes

Reusable parsing templates are another operational improvement: CSV, Excel and JSON settings can be saved, applied and deleted, and Chat2DB now reports format or mapping problems before execution. The beta also adds configurable CSV export encoding and delimiters. Together, those changes can reduce recurring setup errors, but saved templates should be versioned alongside the upstream file contract; a familiar template applied to a changed column layout can still be the wrong configuration. Chat2DB release notes

This is explicitly a beta release, distributed through the “Receive beta versions” setting or downloadable installers. The practical rollout is narrow: test resume after cancellation, test one malformed row and one duplicate key, retain the rejected-row artifact, and reconcile processed, stored and rejected totals before promoting the workflow. Chat2DB release notes

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