8000 Consider removing `read-column-thunk` from the JDBC backend · Issue #83 · camsaul/toucan2 · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Consider removing read-column-thunk from the JDBC backend  #83
New issue
New issue
Open
Open
Consider removing read-column-thunk from the JDBC backend #83
Labels
JDBC backend / next.jdbcIssues related to JDBC and next.jdbc integrationbreaking changeSomething that will affect the API in a possibly breaking waymedium priorityunder considerationPossible ideas that may be implemented in the future
@camsaul

Description

@camsaul
camsaul
opened on Jan 18, 2023

You can specify reader protocols using next.jdbc. It's not as powerful, since it doesn't dispatch off of connection type or model, but it's workable. We should decide if read-column-thunk is really worth the extra moving parts/documentation burden

Metadata

Metadata

Assignees

No one assigned

    Labels

    JDBC backend / next.jdbcIssues related to JDBC and next.jdbc integrationbreaking changeSomething that will affect the API in a possibly breaking waymedium priorityunder considerationPossible ideas that may be implemented in the future

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions
      0