Skip to content
This repository has been archived by the owner on Oct 29, 2024. It is now read-only.

unexpected from_dsn behaviour? #586

Open
sthenault opened this issue May 4, 2018 · 1 comment
Open

unexpected from_dsn behaviour? #586

sthenault opened this issue May 4, 2018 · 1 comment

Comments

@sthenault
Copy link

This is more an open discussion than an issue.

As a newbie influxdb python user, I'm a bit surprised by the from_dsn behavior. I don't get the point of using fake URL like 'influxdb://host:port/database' (unless those are working under some other conditions?). I would have expected it to work with an actual URL. It's still easy to provide extra kwargs to specify e.g. database. or UDP port.

This would be IMHO more intuitive, and could still work with #556.

I can write a patch if we agree on this.

@sthenault
Copy link
Author

sthenault commented May 4, 2018

also, I don't get the point of supporting several hosts separated by comma (_parse_dsn is returning several host information in a 'hosts' key), while this is actually unsupported (from_dsn only keep the fist one) nor undocumented / untested, unless I misunderstood something.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant