[81reap]

With the unstable-sqlx-next feature and SQLPAGE_UNSTABLE_SQLX_NEXT=true, mssql:// and sqlserver:// URLs now run through sqlx 0.9 and the sqlx-sqlserver driver.

sqlx-sqlserver a few workarounds ::

• sqlx-sqlserver encrypts connections with native-tls, so we use OpenSSL instead of rusttls.
• We enable sqlx-core's migrate feature.
• Its connection options have no way to set a password. database_password stops with an error that asks for the password in database_url instead.

Refs #1056

---

_{Stack created with GitHub Stacks CLI • Give Feedback 💬}

[datadog-official]

❌ Errors

Your PR has failed checks. Please review the issues below and take necessary action before merging.

🚦 9 Pipeline jobs failed

CI | docker_build (linux/amd64, duckdb) — 🔧 Needs a code fix, caused by this PR

View more details · View in GitHub Actions

Failed to select a version for libsqlite3-sys due to a conflict with libsqlite3-sys v0.39.1 used by sqlx-core-oldapi v0.6.59, which is required by sqlx in sqlpage v0.48.0. Only one package can link to the native library sqlite3.

CI | docker_build (linux/amd64, minimal) — 🔧 Needs a code fix, caused by this PR

View more details · View in GitHub Actions

Dependency resolution failed for package 'libsqlite3-sys' due to conflict with a previous package linking to 'sqlite3'.

CI | docker_build (linux/arm64, minimal) — 🔧 Needs a code fix, caused by this PR

View more details · View in GitHub Actions

Failed to resolve version for libsqlite3-sys. Conflicting native library sqlite3 linked by multiple packages: libsqlite3-sys v0.39.1 and sqlx-core-oldapi v0.6.59.

View all 9 failed jobs.

📋 Copy fix prompt

CI on my pull request is failing. Help me find and fix the root cause of each failing job below — they were flagged as caused by changes in this PR, so focus on the diff. For each job, explain the failure and propose a fix.

Before you start, set up the Datadog software-delivery tooling so you can
query the CI data yourself:

1. Check whether you already have the Datadog software-delivery MCP tools
   (e.g. a `search_datadog_ci_pipeline_events` tool) and the `unblock-pr` skill.
2. If either is missing, STOP and ask me for permission before installing
   anything. Do not install or run anything until I have said yes.
3. Only with my explicit approval, set up the Datadog software-delivery MCP
   server and skills by following:
     https://docs.datadoghq.com/getting_started/software_delivery_mcp_tools/
   then restart so the skill is picked up.
4. If I decline, skip all of the above and work from the context below alone.

Then run /unblock-pr — it will pull the CI data itself. The job context below is what we already know.

If /unblock-pr is not available — because I declined the setup above, or it did not install — work from the context below instead.

Datadog has already classified this failure as caused by changes in this PR.
Take that as given and work the fix:

1. Locate the change. Diff this branch against its base and find the change
   that produces this error. Explain the mechanism, don't just name a file:
     git fetch origin && git diff $(git merge-base origin/81reap/sqlx-next/5-odbc HEAD)...HEAD
2. Reproduce it locally. Run the failing job's command or test before
   proposing anything.
3. Propose the smallest fix that addresses the root cause — not a workaround,
   not a broadened assertion, not a disabled or skipped test.
4. Re-run the same command to confirm, and say exactly what you ran.
5. If the failure turns out to be intermittent rather than deterministic, say
   so plainly instead of "fixing" it — that is a flaky test, and patching it
   hides the problem.

If the right move is to re-run the job rather than change code, use the job
link in the context below. For GitHub Actions: `gh run rerun <run-id> --failed`,
where the run ID is the number after `/runs/` in that URL (not the trailing
number, which is the job ID).

Branch: 81reap/sqlx-next/6-sql-server

CI | docker_build (linux/amd64, duckdb)
Commit: f1d1cfa0f4f60f2132304c5096c320147c8cec23
Error (code / build):
Failed to select a version for `libsqlite3-sys` due to a conflict with `libsqlite3-sys v0.39.1` used by `sqlx-core-oldapi v0.6.59`, which is required by `sqlx` in `sqlpage v0.48.0`. Only one package can link to the native library `sqlite3`.
CI job: https://github.com/sqlpage/SQLPage/actions/runs/43194763829/job/131102804252

CI | docker_build (linux/amd64, minimal)
Commit: f1d1cfa0f4f60f2132304c5096c320147c8cec23
Error (code / build):
Dependency resolution failed for package 'libsqlite3-sys' due to conflict with a previous package linking to 'sqlite3'.
CI job: https://github.com/sqlpage/SQLPage/actions/runs/43194763829/job/131102804318

CI | docker_build (linux/arm64, minimal)
Commit: f1d1cfa0f4f60f2132304c5096c320147c8cec23
Error (code / build):
Failed to resolve version for `libsqlite3-sys`. Conflicting native library `sqlite3` linked by multiple packages: `libsqlite3-sys v0.39.1` and `sqlx-core-oldapi v0.6.59`.
CI job: https://github.com/sqlpage/SQLPage/actions/runs/43194763829/job/131102804343

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: f1d1cfa | Docs | View more details | Give us feedback!}