feat: Add ODBC build modes and documentation

Co-authored-by: contact <[email protected]>

Author: cursoragent

CONTRIBUTING.md

@@ -37,6 +37,33 @@ cargo build --release
 
 The resulting executable will be in `target/release/sqlpage`.
 
+### ODBC build modes
+
+SQLPage supports three additive build modes for ODBC. Choose the mode via Cargo features:
+
+- Dynamic ODBC (default):
+  - Works on Linux, macOS and Windows (Windows has ODBC built-in).
+  - Command:
+    ```bash
+    cargo build               # or: cargo build --features odbc-dynamic
+    ```
+- Static ODBC (Linux only):
+  - Statically links the ODBC driver manager; simplifies distribution.
+  - Command:
+    ```bash
+    cargo build --features odbc-static
+    ```
+- No ODBC:
+  - Disables ODBC support entirely.
+  - Command:
+    ```bash
+    cargo build --no-default-features
+    ```
+
+Notes:
+- When cross-compiling in Docker, headers come from the base image (e.g. `unixodbc-dev`).
+- Runtime rpath on Linux includes `$ORIGIN/sqlpage:$ORIGIN/lib` so you can colocate drivers next to the binary when needed.
+
 ## Code Style and Linting
 
 ### Rust
@@ -199,8 +226,6 @@ git checkout -b feature/your-feature-name
    - Run frontend linting with Biome
    - Test against multiple databases (PostgreSQL, MySQL, MSSQL)
 
-5. Wait for review and address any feedback
-
 ## Release Process
 
 Releases are automated when pushing tags that match the pattern `v*` (e.g., `v1.0.0`). The CI pipeline will:

README.md

@@ -190,7 +190,7 @@ You can skip this section if you want to use one of the built-in database driver
 
 SQLPage supports ODBC connections to connect to databases that don't have native drivers, such as Oracle, Snowflake, BigQuery, IBM DB2, and many others.
 
-On Linux, the SQLPage binary and Docker image now statically link against the `unixODBC` driver manager, so you generally do not need to install `unixodbc` on the host anymore. You still need to install the database-specific ODBC driver for the database you want to connect to. SQLPage also searches for drivers in a `sqlpage/` directory placed next to the executable (rpath includes `$ORIGIN/sqlpage`). You can drop driver `.so` files there when packaging a self-contained application.
+On Linux, SQLPage supports both dynamic and static ODBC linking. The Docker image uses the system `unixODBC` (dynamic). Release binaries can be built with static ODBC linking by enabling the `odbc-static` feature. You still need to install or provide the database-specific ODBC driver for the database you want to connect to. SQLPage also searches for drivers in a `sqlpage/` directory placed next to the executable (rpath includes `$ORIGIN/sqlpage`).
 
 #### Install ODBC
 

src/webserver/database/connect.rs

@@ -10,11 +10,12 @@ use anyhow::Context;
 use futures_util::future::BoxFuture;
 use sqlx::{
     any::{Any, AnyConnectOptions, AnyKind},
-    odbc::OdbcConnectOptions,
     pool::PoolOptions,
     sqlite::{Function, SqliteConnectOptions, SqliteFunctionCtx},
     ConnectOptions, Connection, Executor,
 };
+#[cfg(feature = "odbc")]
+use sqlx::odbc::OdbcConnectOptions;
 
 impl Database {
     pub async fn init(config: &AppConfig) -> anyhow::Result<Self> {
@@ -209,8 +210,11 @@ fn set_custom_connect_options(options: &mut AnyConnectOptions, config: &AppConfi
     if let Some(sqlite_options) = options.as_sqlite_mut() {
         set_custom_connect_options_sqlite(sqlite_options, config);
     }
-    if let Some(odbc_options) = options.as_odbc_mut() {
-        set_custom_connect_options_odbc(odbc_options, config);
+    #[cfg(feature = "odbc")]
+    {
+        if let Some(odbc_options) = options.as_odbc_mut() {
+            set_custom_connect_options_odbc(odbc_options, config);
+        }
     }
 }
 
@@ -239,6 +243,7 @@ fn make_sqlite_fun(name: &str, f: fn(&str) -> String) -> Function {
     })
 }
 
+#[cfg(feature = "odbc")]
 fn set_custom_connect_options_odbc(odbc_options: &mut OdbcConnectOptions, config: &AppConfig) {
     // Allow fetching very large text fields when using ODBC by removing the max column size limit
     let batch_size = config.max_pending_rows.clamp(1, 1024);