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

doc/md - added usage note for golang-migrate #2482

Merged
merged 5 commits into from Apr 20, 2022
Merged

doc/md - added usage note for golang-migrate #2482

merged 5 commits into from Apr 20, 2022

Conversation

thmeitz
Copy link
Contributor

@thmeitz thmeitz commented Apr 18, 2022

No description provided.

@thmeitz thmeitz changed the title docs - added usage note for golang-migrate doc/md - added usage note for golang-migrate Apr 18, 2022
@a8m a8m requested a review from masseelch April 18, 2022 17:23
@a8m
Copy link
Member

a8m commented Apr 18, 2022

Thanks for the contribution @thmeitz 🙏
I added @masseelch as a reviewer because he wrote this document.

@masseelch
Copy link
Collaborator

🙏


Without the `multiStatements=true` parameter, the migration will fail if there is more than one SQL statement in the migration file.

Please note that all other options you use for your DSN must be added as well!
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd drop this sentence and change the above to something like "you need to add the multiStatements parameter to true as in the example below" and then take the DSN we used in the documents with the param applied. WDYT?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm fine with your change.

@masseelch masseelch merged commit 4e1affe into ent:master Apr 20, 2022
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

Successfully merging this pull request may close these issues.

None yet

3 participants