v1.7.4-legacy — Fix Field Filter numeric-ID SQL (#12) + describe-table diagnostics (#10)
Fixes
-
Issue #12 — Field Filter (
"type": "dimension") template tags in native SQL questions produced invalid SQL that referenced the raw numeric Metabase field ID (TABLE.5503) instead of the column name (TABLE.GRUPO), causingColumn unknownerrors. The[:firebird-legacy :field]HoneySQL method now mirrors the existingtable-namefallback: when:source-aliasisn't in the opts map (as is the case for Field Filter dimensions, which don't route through the MBQL alias middleware), it looks up the field's real name viametabase.lib.metadata/fieldbefore falling back to stringifying the ID. -
Issue #10 diagnostics — added info-level logging in
describe-table(row count from the join, first row shape, and final field count returned to Metabase). If sync is reporting "Table X has no Fields associated with it", the new log lines will show whether the driver's SQL returned zero rows or whether the fields are being lost downstream.
Firebird 1.5 note
Firebird 1.5 doesn't have TRIM(), so the defensive TRIM(rf.RDB$RELATION_NAME) guard added to the standard driver for issue #10 can't be applied here. If you're on Firebird 1.5 – 2.5 and hitting "no Fields associated" symptoms, please file a specific issue with the new log output.
Compatibility
- Metabase 0.57+ (unchanged from 1.7.3-legacy).
- Firebird 1.5 – 2.5 via Jaybird 2.2.15.
Install
Place firebird-legacy.metabase-driver.jar into your Metabase plugins/ directory and restart. Use only one of the standard or legacy drivers at a time — not both side-by-side.