-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use URI to connect to server #43
Comments
I propose |
I agree with the general proposal. I also am OK with having port and protocol specification optional. URIs also allow for username/password specification: |
is the i'm trying out the
|
I am quoting from RFC 3986:
So indeed the |
looks to me like the core monetdb developers need to make a decision here. |
wouldn't it be better to have |
@mlkersten @kutsurak I don't have any strong opinions about this, apart from that the |
Honestly I would prefer the |
To stay within the odbc/jdbc uri scheme we should keep the mapi:monetdb:// etc here |
so the odbc/jdbc URI scheme violates RFC 3986? |
I'm not sure thats how we should interpret the scheme: in this RFC. But as just discussed with Panos, we prefer (for pymonetdb) the sorter simple uri monetdb:// for example. So lets continue that way. That jdbc/odbc requires this is, shouldn't be a problem for the pymonetdb code. Seems we all agree now. |
Keep in mind that the "mapi" scheme has two different types: With this in mind, the URI parses as The hier-part cannot be further broken down according to the generic syntax, so the authority that is defined there does not apply. Perhaps it would be nice if it did, but then we cannot use the parts "monetdb:" and "merovingian:". If we are to simplify the scheme so that we can use the generic syntax for the authority (i.e. username, hostname, port) we need to first remind ourselves how the monetdb and merovingian subschemes are used, and then how we can change those. |
ok, then I'm still not really sure what the consensus here is. Since I want to push out 1.3.0 out today, I'm moving this discussion to 2.0.0 since this is the last blocking issue. |
I was unaware of the discussion in this ticket but last year I submitted a pull request adding support for The PR implemented a libmapi-like mapi:monetdb://... syntax so you can copy/paste from |
It would be nice if the connect() has a variant that can distangle the URI for monetdb, e.g.
pymonetdb.connect(URI=mapi:monetdb://Martins-MacBook-Pro-3.local:50000/sf1)
This can be broken down into host,port, database
The text was updated successfully, but these errors were encountered: