Firebird driver

Offen
  • Stimmt etwas nicht?
#2,261 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
25/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Ruhig
Tech-Stack
sql, swift
Bereich
databases

Rechercherichtung

Read the existing Teradata split in Plugins/ and Packages/TableProCore/Sources/TableProTeradataCore, then review TableProTeradataCoreTests and the Firebird protocol references named in the issue. The work spans a new protocol core, plugin integration, build and registry wiring, docs, and tests; done means the listed Firebird versions and standard driver operations are supported, with codec/auth tests and manual server verification.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

enhancement platform-macos
Problem

Firebird is not supported. No Firebird plugin exists under apple/Plugins/, and nothing in the repo references Firebird. Asked for in discussion #2257.

Firebird still runs under many older desktop and ERP deployments. Demand so far is one user, so this is a backlog item, not urgent.

Proposed solution

A registry-only FirebirdDriverPlugin, with the wire protocol written in Swift as apple/Packages/TableProCore/Sources/TableProFirebirdCore, the same split TeradataDriverPlugin and TableProTeradataCore use (#1888).

Scope for v1

  • Firebird 3.0, 4.0 and 5.0 over TCP 3050, wire protocol 13 and up.
  • Auth: Srp256 and Srp.
  • Wire encryption: ChaCha, ChaCha64 and Arc4.
  • Database path or alias, user, role and charset on the connection form.
  • Tables, views, procedures, triggers, generators and domains in the sidebar.
  • Firebird's own dialect in the editor and in generated DDL.
  • Browse, query, edit, structure, DDL, export and import through the standard driver surface.

Protocol core

  1. XDR reader and writer, op codes for protocol 13 through 19.
  2. op_connect / op_accept_data / op_attach handshake, including the multi-step auth exchange.
  3. SRP-6a (Srp256, Srp). BigUInt.modPow already exists in TableProTeradataCore (apple/Packages/TableProCore/Sources/TableProTeradataCore/BigUInt.swift:150) and moves to a shared target.
  4. Wire encryption. Firebird 3.0 defaults WireCrypt to Enabled and 4.0 defaults it to Required, so a driver without it cannot reach a stock 4.0 or 5.0 server. SRP hands over a 160-bit key and ChaCha takes the first 128 bits of it.
  5. BLR message descriptions for parameters and result rows.
  6. Statement prepare, execute, fetch, and the blob round trips (op_open_blob2, op_get_segment).
  7. Type decoding: NUMERIC and DECIMAL as scaled integers, DATE and TIMESTAMP as modified Julian, DECFLOAT and INT128 on 4.0, per-column charsets including NONE.

Plugin

  1. Schema reads over RDB$RELATIONS, RDB$RELATION_FIELDS, RDB$FIELDS, RDB$INDICES, RDB$RELATION_CONSTRAINTS, RDB$TRIGGERS, RDB$PROCEDURES, RDB$GENERATORS.
  2. Pagination with ROWS, or OFFSET/FETCH on 4.0 and up.
  3. Identifier quoting, including the unquoted-folds-to-upper rule.
  4. One connection is one database file, so the tree is flat like SQLite and DuckDB. Firebird 6.0 adds SQL schemas (RDB$SCHEMAS); leave room for that instead of designing it in now.

Wiring

What every new driver needs: the apple/project.yml target and its RegistryPlugins entry, a DatabaseType constant, an entry in .github/plugin-registry.json, a curated snapshot in apple/TablePro/Core/Plugins/PluginMetadataRegistry+RegistryDefaults.swift (without it the type never appears in the New Connection picker), the TableProProvidesDatabaseTypeIds key in the plugin's Info.plist, an icon asset, databases/firebird.mdx and a row in databases/index.mdx through a paired docs PR, and a fragment in apple/changelog.d/.

Risks

  • Wire encryption is a gate, not an extra. It is the easiest part of the estimate to get wrong.
  • The official wire protocol spec (v0.18) says it is incomplete and that higher protocol versions are only partially described. nakagami/firebirdsql (Go, MIT), Jaybird and node-firebird are the cross checks.
  • Firebird 2.5 uses protocol 10 to 12 and legacy auth, a separate code path. Left out of v1.
  • An embedded .fdb file with no server cannot work over a socket driver. The docs page needs to say so.

Testing

Unit tests over the codecs and auth vectors in a new TableProFirebirdCore test target. The macOS CI runs no database services, so server verification is manual against Firebird 3.0, 4.0 and 5.0 in Docker.

Out of scope for v1

Firebird 2.5, events, the services API (backup and restore), array columns.

After v1: embedded databases

Opening a local .fdb file with no server running. This needs the embedded engine in libfbclient, with the costs listed under Alternatives considered, so it waits until the socket driver ships.

Alternatives considered
  • Link libfbclient. On macOS it installs as a system framework at /Library/Frameworks/Firebird.framework, so users would have to install Firebird themselves. Bundling it instead means building a static universal slice that Firebird does not support building, and it pulls in ICU, libtommath, libtomcrypt and a C++ runtime. The only thing it buys is embedded .fdb files.
  • A Rust bridge over rsfbclient with its pure Rust backend, the shape apple/Native/DamengBridge uses. Workable, but the crate's wire encryption support is not documented, and that is the one part we cannot ship without. It needs to be verified before choosing it.
  • Today: isql-fb on the command line.
Platform

macOS

Related database type

N/A / General

Vorherrschende Sprache
Swift
Sterne
6.2k
Forks
412
Ø Merge
3 Std. 56 Min.
Gemergte PRs (30 T.)
669

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus TableProApp/TablePro

Alle Issues in TableProApp/TablePro

Ähnliche Issues

Weitere Issues zu Swift

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.