As of #22 we have a Postgres interface that gets username, port, host IP and password from a private credential file, the database connection name from the main config.py, and the specific schema and table to read from manually passed to the constructor. This is a terrible API and should be replaced, but we need to see how to implement Postgres hooks in Kedro before designing a better system, since it may already have a more consistent system in place.
As of #22 we have a Postgres interface that gets username, port, host IP and password from a private credential file, the database connection name from the main
config.py, and the specific schema and table to read from manually passed to the constructor. This is a terrible API and should be replaced, but we need to see how to implement Postgres hooks in Kedro before designing a better system, since it may already have a more consistent system in place.