View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000045 | Inlyra Studio | Database Connections | public | 2026-09-26 22:44 | 2026-09-26 22:44 |
| Reporter | inlyradev | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Target Version | v1.1.0 | ||||
| Summary | 0000045: Add ODBC support for generic database connectivity | ||||
| Description | Add ODBC connectivity to Inlyra Studio Pro to support databases and data sources that do not yet have a native Inlyra connector. ODBC should be positioned as a broad-compatibility connector, while native database providers remain the preferred option for best performance, provider-specific features, and support. Initial implementation should support both Windows DSN-based connections and DSN-less connection strings. Proposed functionality: - Add ODBC as a supported database connection type. - Support: - Windows User DSNs - Windows System DSNs - DSN-less connection strings - When DSN mode is selected: - enumerate configured ODBC DSNs on the local machine - display available DSNs in a dropdown - identify User vs System DSNs where possible - provide a Refresh option - Allow Username and Password entry when credentials are not stored in the DSN. - Provide a Test Connection action. - Allow saved ODBC connections to be reused across workflows. - Support ODBC Input and ODBC Output operations. - Reuse the redesigned database connection-management UI where practical. Example workflow: Connect to an existing Windows ODBC DSN such as FinanceWarehouse, read a table or supported query, transform the data in Inlyra, and write the results to another supported destination. Design considerations: - Native connectors such as SQL Server, PostgreSQL, MySQL, and MariaDB should remain preferred when available. - ODBC should be treated as a generic compatibility option and may not provide the same performance or provider-specific capabilities as native connectors. - Error handling should surface driver and connection errors clearly, since ODBC behavior may vary by installed driver. - Consider whether driver architecture differences such as 32-bit vs 64-bit need to be detected or documented. | ||||
| Tags | No tags attached. | ||||
| Report Type | Enhancement | ||||
| Edition | Both | ||||
| Operating System | Windows 11 | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-09-26 22:44 | inlyradev | New Issue |