When running RoundhousE against Azure Database providing connection string via /connstring parameter, it incorrectly identifies database name (uses server name).
STR:
Execute roundhouse against Azure PostgreSQL Database server
REASON:
This piece of code parses the connection string using "keywords" like Host, Database but in azure the server URL does contain 'Database' and the logic breaks
I suppose NpgsqlConnection can be used to parse the string properly
WORKAROUND:
If Database goes first in the connection string then the problem can be avoided. So something like this "Database=Roundhouse;Host=test.postgres.database.azure.com;User ID=postgres;Password=;" works
When running RoundhousE against Azure Database providing connection string via /connstring parameter, it incorrectly identifies database name (uses server name).
STR: Execute roundhouse against Azure PostgreSQL Database server
REASON: This piece of code parses the connection string using "keywords" like Host, Database but in azure the server URL does contain 'Database' and the logic breaks I suppose NpgsqlConnection can be used to parse the string properly
WORKAROUND: If Database goes first in the connection string then the problem can be avoided. So something like this "Database=Roundhouse;Host=test.postgres.database.azure.com;User ID=postgres;Password=;" works