Skip to content

README: Include Difference in Connection Strings depending on Cloud SQL Generation #485

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

Merged
merged 3 commits into from
Oct 25, 2016

Conversation

lennrt
Copy link
Contributor

@lennrt lennrt commented Sep 26, 2016

Description

I updated the information in the README.md file to reflect the different connection strings for different generations of Google Cloud SQL servers.

For a Second Generation Google Cloud SQL server one should use this connection string:
user@cloudsql(project-id:regionname:instance-name)/dbname

For a First Generation Google Cloud SQL server one should use this connection string:
user@cloudsql(project-id:instance-name)/dbname

Checklist

  • Code compiles correctly
  • Created tests which fail without the change (if possible)
  • All tests passing
  • Extended the README / documentation, if necessary
  • Added myself / the copyright holder to the AUTHORS file

Fixes #481, #484

…ration

Google Cloud SQL servers have different connection strings depending on whether they are a First Generation MySQL server or a Second Generation MySQL server.
@lennrt lennrt changed the title Updated Readme: Include Difference Updated Readme: Include Difference in Connection Strings depending on Cloud SQL Generation Sep 26, 2016
@julienschmidt julienschmidt modified the milestone: v1.3 Oct 25, 2016
@julienschmidt julienschmidt changed the title Updated Readme: Include Difference in Connection Strings depending on Cloud SQL Generation README: Include Difference in Connection Strings depending on Cloud SQL Generation Oct 25, 2016
@julienschmidt julienschmidt merged commit 1983bc3 into go-sql-driver:master Oct 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants