You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the test set for PostgreSQL support via LibPQ.jl does not exist yet. We need a test set that covers the following functions within postgresql.jl:
_dbconnect - this function is the core dispatch within DBConnector.jl and is exported for a user
To create tests initially, a PostgreSQL database can be used either locally or on a server. Most likely for those interested in addressing this problem, one will have to set-up a local PostgreSQL instance for testing.
Furthermore, it will generally be difficult to create tests individually for each of these functions so we could perhaps instead adopt an integration test approach where we have a test set that relies on each of these three functions working together.
The text was updated successfully, but these errors were encountered:
Until this PR is finished, we may have to use this fork until this functionality is merged into LibPQ itself: https://github.com/chris-b1/LibPQ.jl#dbinterface. But, that should unblock the complications in adding this feature.
Farreeda
pushed a commit
to Farreeda/DBConnector.jl
that referenced
this issue
Jul 3, 2023
Currently, the test set for PostgreSQL support via LibPQ.jl does not exist yet. We need a test set that covers the following functions within
postgresql.jl
:DBInterface.connect
- this is based off of the documentation for the DBInterfaceconnect
functionDBInterface.prepare
- this is based off of the documentation for the DBInterfaceprepare
functionDBInterface.execute
- this is based off of the documentation for the DBInterfaceexecute
function_dbconnect
- this function is the core dispatch within DBConnector.jl and is exported for a userTo create tests initially, a PostgreSQL database can be used either locally or on a server. Most likely for those interested in addressing this problem, one will have to set-up a local PostgreSQL instance for testing.
Furthermore, it will generally be difficult to create tests individually for each of these functions so we could perhaps instead adopt an integration test approach where we have a test set that relies on each of these three functions working together.
The text was updated successfully, but these errors were encountered: