Comparing v0.1.2...v0.1.3 · Altinity/altinity-sql-browser · GitHub
Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: Altinity/altinity-sql-browser
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.1.2
Choose a base ref
...
head repository: Altinity/altinity-sql-browser
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.1.3
Choose a head ref
  • 2 commits
  • 6 files changed
  • 3 contributors

Commits on Jun 28, 2026

  1. fix(schema): draw every table in a whole-DB graph, linked or not (#63)

    * fix(schema): draw every table in a whole-DB graph, linked or not
    
    The data-flow graph dropped tables that didn't participate in any
    view/MV/dictionary/Distributed relationship whenever the database had *some*
    lineage — so a database of mostly-standalone tables showed only the few linked
    boxes and hid the rest. Reverses that pruning: a whole-DB view now keeps every
    object as a node, drawing lineage edges between the linked ones and standalone
    cards for the rest (matching the no-relationships case, which already did this).
    
    Table-focus (1-hop neighbourhood) is unchanged — it's a deliberately scoped view.
    Cross-DB scoping in the full view is still handled by expandLineage, which seeds
    the focus DB and BFS-walks only the connected nodes of other databases, so this
    doesn't pull unrelated tables in from neighbouring databases.
    
    Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
    Claude-Session: https://claude.ai/code/session_019kE9qbgBNBrfNgwg9fRsMJ
    
    * fix(schema): pack unlinked tables below the lineage + drop redundant db prefix
    
    Two UX refinements on the whole-DB graph:
    
    - Lay the connected lineage out first and grid the edge-less "single" tables
      beneath it (new `isolatedLast` option on dagreLayout, used by both the inline
      preview and the full view), instead of dagre ranking the orphans across the top.
    - Drop the redundant "<db>." prefix from a node's label when it's in the focused
      database; nodes from another database keep their qualified id so the cross-DB
      origin stays visible. Applied once in buildSchemaGraph, so both the inline short
      view and the full-view cards pick it up. ids/edges (and click-to-SHOW-CREATE)
      are unaffected — only the display label changes.
    
    Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
    Claude-Session: https://claude.ai/code/session_019kE9qbgBNBrfNgwg9fRsMJ
    
    ---------
    
    Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
    BorisTyshkevich and claude authored Jun 28, 2026
    Configuration menu
    Copy the full SHA
    b01cf27 View commit details
    Browse the repository at this point in the history
  2. chore(release): 0.1.3

    Schema data-flow graph improvements (#63): the whole-DB graph now draws every
    table (linked or not), packs the unlinked "single" tables into a grid below the
    lineage, and drops the redundant "<db>." prefix from node labels for objects in
    the focused database (cross-DB nodes stay qualified). No new runtime deps.
    
    Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
    Claude-Session: https://claude.ai/code/session_019kE9qbgBNBrfNgwg9fRsMJ
    BorisTyshkevich and claude committed Jun 28, 2026
    Configuration menu
    Copy the full SHA
    50a8bdf View commit details
    Browse the repository at this point in the history
Loading