Thomas Karner
Thomas Karner
@parsiazare I see some open issues regarding sslmode in the used pgx package - I will look into it
It is possible to expand env variables in the connection string (https://github.com/spf13/viper/issues/119#issuecomment-417638360) I could already confirm that it works and I added an integration test to test the ssl connection...
Expanding env variables is now available in [version 0.4.0](https://github.com/KarnerTh/mermerd/releases/tag/v0.4.0) @sachasmart-weavik The example from your last comment should work now - please let me know if does not :)
I have a similar idea in mind, but have not started implementing it yet. It should play well with the existing feature to display the constraint name in the column...
Glad you find the tool useful :) All supported databases are automatically tested via the integration tests (but with a defined set of tables, so not all edge cases are...
Would it be ok if the schema selection would be the same as for the tables? - multiselection via cli - list of schemas in (run-)config - a `--useAllSchemas` flag...
Would love to have vim bindings in beekeeper studio :) any updates?
Sry for the late response I am not an expert regarding MSSQL, but according to the docs it should work like that `sqlserver://username:password@host/instance?param1=value¶m2=value` (Source [here](https://github.com/denisenkom/go-mssqldb#connection-parameters-and-dsn)) Have you tried to add...
Any update on the issue? Does it work now?
Same problem here with serverless lambda functions - any updates or workarounds?