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
Custom mapping types confuse Doctrine identifying schema changes #6077
Comments
Simply by adding this function: /**
* {@inheritdoc}
*/
public function requiresSQLCommentHint(AbstractPlatform $platform)
{
return !parent::requiresSQLCommentHint($platform);
} |
Sufficient: /**
* {@inheritdoc}
*/
public function requiresSQLCommentHint(AbstractPlatform $platform)
{
return true;
} |
@Ocramius , yes, sufficient... But the editor told me I were not calling the parent method and I don't like alerts. The result is the same. |
That's a false positive - don't blindly trust the editor. On 8 Oct 2016 1:16 p.m., "Adamo Crespi" notifications@github.com wrote:
|
Eh eh, yes, I know, but anyway it alerts me and, as told, I don't like have superflous alerts. So, if I can"solve" them, I do, so I know what really has to have attention reserved... |
As told in the title, I've created two custom mapping types.
Now, each time I run the schema validation, Doctrine thinks the field that use those custom types have to be updated.
I've described the problem in full details on StackOverflow.
I don't know if this is a fault of mine or a Doctrine's one, so I'm writing this issue.
Thank you.
The text was updated successfully, but these errors were encountered: