-
Notifications
You must be signed in to change notification settings - Fork 2.3k
mysql.NewConnector not exposed without build tags #1013
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
Comments
Why do you want to remove the build tag? |
Mostly so the library I'm building doesn't force everyone that leverages it to use a build tag. I feel that enforcing some constraints on the consumer's build process due to implementation details on my end would make for a poor API. Is there any reason that it has a build tag, given that the only supported versions are 1.13, 1.12 and 1.11 from what I can tell? |
Do you mean you need to do something to use build tag??? |
What "enforcing some constraints" means?
Because we supported Go 1.9 (for legacy GAE/Go). But it just removes some binary size. |
Huh, must be an issue with my setup. I'll have to look into it on my end 😅 I'll submit a PR in the next few days - thanks! |
FYI - implementing in #1016. From what I can tell, merging it would be a BC break as you'd be dropping support for 1.9. Please let me know whether or not I should go ahead with the changes. |
Maybe, you are using tagged version (1.4) which doesn't have connector.
Why is it breaking change? While |
I managed to isolate it to being an issue with my IDE. It's not great, but I can work around it. IIRC, go 1.9 doesn't contain the |
It looks like
mysql.NewConnector
is only exposed when built with the build taggo1.10
. Is there any chance you can remove the build constraint from it?I'm happy to submit a PR if it's easier that way.
The text was updated successfully, but these errors were encountered: