Upgrade sqlx and implement db detection#1024
Conversation
This commit introduces support for ODBC databases, allowing users to connect to a wider range of data sources. It also includes updates to various dependencies, ensuring the project is using the latest stable versions and incorporating necessary bug fixes and performance improvements. Co-authored-by: contact <contact@ophir.dev>
|
Cursor Agent can help with this pull request. Just |
|
@cursoragent Make sure you update CI to be able to build with odbc https://github.com/sqlpage/sqlx-oldapi?tab=readme-ov-file#odbc-setup test locally with an odbc data source |
|
❌ Unable to add follow-up after multiple attempts. The agent may be experiencing issues. Please try again later or check the agent status. Learn more about Cursor Agents |
…se SupportedDatabase enum for improved database type management and placeholder generation.
…ny_kind for improved clarity and consistency.
…mproved database support
Co-authored-by: Cursor Agent <cursoragent@cursor.com>
…w to include ODBC testing
|
@cursoragent docker ci failed with and the odbc tests fail with read the docs for the connection string to use with the ubuntu postgres driver you installed. |
|
I improved the Docker build process and enhanced CI stability. I ensured that the
Learn more about Cursor Agents |
Co-authored-by: contact <contact@ophir.dev>
…rtedDatabase for improved flexibility and clarity in connection options.
…or improved clarity and consistency across database operations.
…oss filesystem and SQL modules for improved clarity and flexibility.
… of environment variable for improved consistency and clarity.
…ouse, MongoDB, and DuckDB.
…cross-compilation
…pdating BINDGEN_EXTRA_CLANG_ARGS
Upgrade sqlx to 0.6.49-beta, enable ODBC support, and introduce a
SupportedDatabaseenum for explicit database type detection.This upgrade enables support for ODBC connections, expanding the range of databases SQLPage can connect to. The new
SupportedDatabaseenum anddetect_database_typemethod leverage sqlx'sdbms_name()API for more precise runtime database identification, with fallbacks toAnyKindwhere necessary. This provides a more robust and type-safe way to handle different database backends.