You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jira issue originally created by user dchesterton:
The schema update tool does not consider the possibility that MySQL double/float fields can be unsigned.
When running the CLI tool, it recognises that the schemas differ but it doesn't add the appropriate 'UNSIGNED' SQL statement. For example when the database is SIGNED but the entity is marked as UNSIGNED, running the tool with --dump-sql will generate SQL similar to below:
ALTER TABLE tablename CHANGE field field DOUBLE PRECISION NOT NULL;
Running this has no effect on the database and subsequent calls will try to run the same SQL.
I have created a pull request in GitHub which fixes the issue.
The text was updated successfully, but these errors were encountered:
Ocramius
changed the title
DBAL-1082: SchemaTool does not generate SQL for MySQL unsigned float
DBAL-1082: SchemaTool does not generate DDL for MySQL unsigned floatJul 22, 2017
Jira issue originally created by user dchesterton:
The schema update tool does not consider the possibility that MySQL double/float fields can be unsigned.
When running the CLI tool, it recognises that the schemas differ but it doesn't add the appropriate 'UNSIGNED' SQL statement. For example when the database is SIGNED but the entity is marked as UNSIGNED, running the tool with --dump-sql will generate SQL similar to below:
ALTER TABLE tablename CHANGE field field DOUBLE PRECISION NOT NULL;
Running this has no effect on the database and subsequent calls will try to run the same SQL.
I have created a pull request in GitHub which fixes the issue.
The text was updated successfully, but these errors were encountered: