Open up access to the underlying NpgsqlConnection

[devonbessemer]

Describe the feature

This library abstracts away the underlying NpgsqlConnection and does not expose the underlying methods. This means we lose access to specific Npgsql methods such as binary import and export methods. Is there a way to still provide public access to an NpgsqlConnection instance?

Use Case

NpgsqlConnection has additional methods for postgres specific operations that are not included in the DbConnection interface

Proposed Solution

Is there a way to still provide public access to an NpgsqlConnection instance?

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

The AWS Advanced .NET Data Provider Wrapper version used

1.0.1

dotnet version used

10

Operating System and version

n/a

[kenrickyap]

Thanks for the suggestions, we will look into adding this functionality for the next release. Our approach will be to expose an unwrap function similar to what is done in the JDBC driver that will return the underlying connection object. Would this solution be sufficient for your use case?

[devonbessemer]

@kenrickyap That sounds sufficient. Just for clarity, there would be some Unwrap<T>() like-method on the AwsWrapperConnection<T> that would return the underlying NpgsqlConnection to operate on?

[kenrickyap]

@devonbessemer Hi sorry for the delayed reply. Yes that is correct, we have just merged in this PR to achieve this: #238.

It should be released with the next version of the wrapper