When adding a second Postgres adapter and defining a Data Asset using it the system will query the postgres adapter that was defined first.
Steps to reproduce:
fresh open data connector environment
add Potgres adapter 'x' for a database running outside the scope of the docker-compose environment
add Data Asset 'a' using adapter 'x'
download ids data under Data Assets for asset 'a' works
add second Postgres adaper 'y' such as the example in the repository (db - ids)
add Data Aseet 'b' (e.g. select * from job)
trying to download asset 'b', the system will query the database behind adapter 'x' instead of 'y'
When creating a dummy table "job" in the database for adapter 'x' it will be delivered as a result for a download of 'b'
When adding a second Postgres adapter and defining a Data Asset using it the system will query the postgres adapter that was defined first. Steps to reproduce:
When creating a dummy table "job" in the database for adapter 'x' it will be delivered as a result for a download of 'b'