Skip to content

Partial transaction support on NeonHTTPDialect #13

@kpietraszko

Description

@kpietraszko

While the neon() function (HTTP) doesn't support real transactions, it does support so called "non-interactive transactions" through a transaction() function.
See docs here

Do you think it would possible to support it?

As a workaround, you could add an option to pass an existing neon query object to the dialect. So the user could call neon(), pass the result to the dialect constructor, and still have access to transaction().

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions