Fixing bug with mysql and default null value for not null columns #39
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JohnRoesler
approved these changes
Nov 18, 2024
manuelarte
deleted the
35-bug-mysql-doesnt-treat-null-as-a-valid-default-for-not-null-fields
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this do?
Which issue(s) does this PR fix/relate to?
Resolves #35
List any changes that modify/break current functionality
Have you included tests for your changes?
There are test that test the automigration gorm functionality for MySQL.
Did you document any new/modified functionality?
N/A
example_test.goREADME.mdNotes
I removed the default:null gorm tags in the struct and added a BeforeCreate hook to check for the mandatory fields