Skip to content
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

Official policy towards URI reserved characters #107

Open
the-Arioch opened this issue May 12, 2020 · 2 comments
Open

Official policy towards URI reserved characters #107

the-Arioch opened this issue May 12, 2020 · 2 comments

Comments

@the-Arioch
Copy link

This module seems to used URI-styled Firebird conneciton strings.
"Seems" because it is not documented on pkg.go.dev at all.

This however creates uncertainty when filename contains "Reserved Characters" as per ch.2.2. of the URI standard - http://tools.ietf.org/html/rfc3986#section-2.2

See for example https://stackoverflow.com/questions/61718778/firebirdsql-cannot-connect-to-database-if-path-contains-hash-symbol

May i suggest that the parameters for Sql.Open be explicititly documented ?
Including official stance on abiding/ignoring certain URI componnts and the very URI standard.
And including some external links describing possible FB connection strings for novices.

@nakagami
Copy link
Owner

Sorry, I don't even know exactly.

I am also looking for documentation pull requests.

@the-Arioch
Copy link
Author

No one can KNOW about the project strategic gaols and directions, it is the leader who leads and decides what is correct and incorrect :-)

Then the behavior that does not match the arbitrary selected goal would begame a bug.
Not the other way around.

First thing is that the project has to decide and declare which way is correct and which is not.

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

No branches or pull requests

2 participants