-
Notifications
You must be signed in to change notification settings - Fork 5.1k
What's new in 0.38.0 for Metabase driver authors
Changes in 0.38.0 mainly relate to the removal of deprecated methods.
If your driver worked on 0.37.x, but fails on 0.38.0 with an error like No suitable driver found for ...
, then it's likely because it's implementing one of the deprecated methods mentioned below that were removed in 0.38.0.
-
metabase.driver.sql.query-processor/unix-timestamp->timestamp
was removed (after being deprecated since 0.35.0).
Usemetabase.driver.sql.query-processor/unix-timestamp->honeysql
instead. -
metabase.driver/date-add
was removed (after being deprecated since 0.34.2). Usemetabase.driver.sql.query-processor/add-interval-honeysql-form
instead. -
metabase.driver.sql.query-processor/current-datetime-fn
was removed (after being deprecated since 0.34.2). Usemetabase.driver.sql.query-processor/current-datetime-honeysql-form
instead.
-
Also of note, there is now support for casting ISO8601 strings as timestamp.
See https://github.com/metabase/metabase/pull/13860 for more details. -
SQL-based drivers may need to add implementations for the new method
metabase.driver.sql.query-processor/cast-temporal-string
to support casting string columns toDATE
s,TIME
s, orTIMESTAMP
s. The default implementations useCAST(<column> AS <type>)
; provide an implementation if your driver needs to do something different. -
For convenience, JDBC-based drivers can now implement
metabase.driver.sql-jdbc.sync/db-default-timezone
, which takes aConnection
, rather thanmetabase.driver/db-default-timezone
- Backend
- Metabase Developer Reference
- Product Management
- QA and Testing
- Writing A Driver
- Driver Notices
- REST API Notices
- Writing style guide for documentation and blog posts (WIP)