Skip to content

armgit / dbx

Public Imported from GitHub
0

25 MB lightweight cross-platform database client for 100+ databases, including MySQL, PostgreSQL, SQLite, Redis, MongoDB, DuckDB, SQL Server, and Dameng. Built-in AI, MCP Server, CLI, desktop and Docker. | 轻量级跨平台数据库管理工具,支持 MySQL、PostgreSQL、SQLite、Redis、MongoDB、达梦等 100+ 数据库,提供桌面端、Docker、CLI、内置 AI 助手和 MCP。

2.2 KB
Raw Blame
import { DBX_ROWID_COLUMN } from "@/lib/table/tableEditing";
import { isQueryExecutionErrorResult } from "@/lib/query/queryResultError";
import type { QueryResult } from "@/types/database";

/**
 * Per-connection memory of engines that rejected the synthetic row-id locator.
 *
 * Keyless PostgreSQL-family tables are opened with a `tableoid`/`ctid`/`xmin`
 * locator projection (see buildTableSelectSql). PostgreSQL-compatible engines
 * without system-column support — Hologres' query translation layer rejects
 * `tableoid` (issue #12647) — fail every such table open with a db error.
 * On the first failure the grid retries once without the locator; a successful
 * retry remembers the connection so later opens skip the locator entirely
 * (keyless tables stay read-only there). Engines that also reject the
 * fallback restore the flag so the user sees the real server error again.
 */
const rowIdLocatorUnsupportedConnections = new Set<string>();

export function rowIdLocatorUnsupported(connectionId: string): boolean {
  return rowIdLocatorUnsupportedConnections.has(connectionId);
}

export function markRowIdLocatorUnsupported(connectionId: string): void {
  rowIdLocatorUnsupportedConnections.add(connectionId);
}

export function markRowIdLocatorSupported(connectionId: string): void {
  rowIdLocatorUnsupportedConnections.delete(connectionId);
}

export function resetRowIdLocatorStateForTests(): void {
  rowIdLocatorUnsupportedConnections.clear();
}

/** A failed data load whose SQL carried the locator is the retry trigger. */
export function shouldRetryWithoutRowIdLocator(sql: string, result: QueryResult | undefined | null): boolean {
  // The connection capability may have been updated by another tab while this
  // locator query was already in flight. The SQL itself is the authoritative
  // record of what was sent; every failed locator-bearing request still needs
  // its own fallback.
  return sql.includes(DBX_ROWID_COLUMN) && !!result && isQueryExecutionErrorResult(result);
}

/** Only a successful fallback keeps the flag; a failed one shows the real error. */
export function shouldKeepRowIdLocatorDisabled(result: QueryResult | undefined | null): boolean {
  return !!result && !isQueryExecutionErrorResult(result);
}