This repository has been archived by the owner on Nov 15, 2019. It is now read-only.
Bug fix for MySQL timestamps with Doctrine1 #44
Closed
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
…ration, doctrine thinks all of my timestamps have changed. I discovered that in Doctrine/Migration/Diff.php on line 214, you check for I therefore devised this solution which will observe whether or not a field is a timestamp field. If so, it will forcibly remove the empty fields. This was my best guess at a resolution and it works for m
…alues and also a fix for string columns... doctrine assigns all fields a unsigned property which causes problems with migrations and behaviors. With the unsigned property, I was setting that at runtime a unsigned validator was checking the values of STRINGS to make sure they were numeric. This changeset will observe if the field type is string and remove the unsigned property during the change detection.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Each time I run a diff migration, doctrine thinks all of my timestamps have changed. I discovered that in Doctrine/Migration/Diff.php on line 214, you check for
I therefore devised this solution which will observe whether or not a field is a timestamp field. If so, it will forcibly remove the empty fields. This was my best guess at a resolution and it works for me.
This problem is also described a long time ago here:
http://groups.google.com/group/doctrine-user/browse_thread/thread/7df8a94284cf89aa?pli=1