Skip to content

refactor(rust): connection registry hygiene before next driver #1949

Closed

Description

@ZhuchkaTriplesix

Summary

Clean the SQLite connection layer before Postgres/MySQL land: registry lock scope, thin IPC commands, one query entrypoint, typed rusqlite errors, trim premature stubs.

Checklist

  • Arc sessions; release map lock before SQLite I/O
  • db_execute_query via session API (no rusqlite in commands)
  • Single error contract for streaming (invoke Err only — no dual Error event)
  • From<rusqlite::Error>
  • Trim unused exports / align DriverKind stubs
  • Clippy -D warnings in tauri-ci
  • Tests green

Parent

#1843 / #1846

Activity

  1. added
    P1High priority / Core capability
    tauriTauri 2 / apps/tauri migration track
    rustRust backend (src-tauri / crates)
    on Nov 15, 2026
  2. added a commit that references this issue on Nov 15, 2026
  3. ZhuchkaTriplesix commented on Nov 15, 2026

    @ZhuchkaTriplesix
    MemberAuthor

    Landed on epic/tauri-migration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1High priority / Core capabilityrustRust backend (src-tauri / crates)tauriTauri 2 / apps/tauri migration track

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions