DDC-1622: Doctrine 2.1 CLI orm:schema-tool update/create reverses scale and precision values for decimal columns #2040

Closed
opened 2026-01-22 13:38:18 +01:00 by admin · 3 comments
Owner

Originally created by @doctrinebot on GitHub (Jan 26, 2012).

Originally assigned to: @beberlei on GitHub.

Jira issue originally created by user fosberyi:

This property definition (or anything with decimal, scale and precision defined):
/****
* @var decimal $cost
*
* @Column(name="cost", type="decimal", scale=6, precision=2, nullable=true)
*/
private $cost;

Produces this in the orm:schema-tool CLI:

ALTER TABLE items CHANGE cost cost NUMERIC(2, 6) DEFAULT NULL, ...

Which fails. Have to go through the SQL code and change manually.

Originally created by @doctrinebot on GitHub (Jan 26, 2012). Originally assigned to: @beberlei on GitHub. Jira issue originally created by user fosberyi: This property definition (or anything with decimal, scale and precision defined): /**** \* @var decimal $cost * \* @Column(name="cost", type="decimal", scale=6, precision=2, nullable=true) */ private $cost; Produces this in the orm:schema-tool CLI: ALTER TABLE items CHANGE cost cost NUMERIC(2, 6) DEFAULT NULL, ... Which fails. Have to go through the SQL code and change manually.
admin added the Bug label 2026-01-22 13:38:18 +01:00
admin closed this issue 2026-01-22 13:38:19 +01:00
Author
Owner

@doctrinebot commented on GitHub (Jul 8, 2012):

Comment created by @beberlei:

You mixed up scale and precision.

@doctrinebot commented on GitHub (Jul 8, 2012): Comment created by @beberlei: You mixed up scale and precision.
Author
Owner

@doctrinebot commented on GitHub (Jul 8, 2012):

Issue was closed with resolution "Invalid"

@doctrinebot commented on GitHub (Jul 8, 2012): Issue was closed with resolution "Invalid"
Author
Owner

@mscodemonkey commented on GitHub (May 27, 2019):

Is this still a bug because i'm still having to reverse scale and precision to make it create it correctly in the database when creating migrations.

E.g.

<field name="value" type="decimal" column="value" scale="11" precision="2" nullable="false"/>

when creating a migration generates the following code for postgresql...

$this->addSql('ALTER TABLE payment ALTER value TYPE NUMERIC(2, 11)');

@mscodemonkey commented on GitHub (May 27, 2019): Is this still a bug because i'm still having to reverse scale and precision to make it create it correctly in the database when creating migrations. E.g. `<field name="value" type="decimal" column="value" scale="11" precision="2" nullable="false"/>` when creating a migration generates the following code for postgresql... `$this->addSql('ALTER TABLE payment ALTER value TYPE NUMERIC(2, 11)');`
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#2040