DDC-2135: Setting column defaults using options in the annotations causes redundant alter statements #2688

New Issue

admin · 2026-01-22T14:00:36+01:00

admin commented

2026-01-22 14:00:36 +01:00

Originally created by @doctrinebot on GitHub (Nov 9, 2012).

Originally assigned to: @beberlei on GitHub.

Jira issue originally created by user ccomer:

When using the Column annotation on an entity and passing the options parameter to set a default value for a column, the doctrine cli will generate the alter statement every time the schema-tool is run.

This doesn't break the functionality of updating the schema using the cli but when you have multiple entities using default values in this manner it becomes cumbersome to investigate issues during updates that fail and you need to dump the generated sql to examine.

Use case: We have a number of entities that include 'boolean' flags. The data for these entities is inserted into the database through an integration process handled by another application. For all of the flags we want to set a default value of 0 to avoid having to modify the integration scripts when a new flag is added to an entity and the data is not available yet.

Example entity:

/****
 * @ORM\Entity
 * @ORM\Table(name="example")
 */
class Example
{

    /****
     * @ORM\Id
     * @ORM\Column(type="integer")
     */
    protected $id;

    /*** @ORM\Column(type="integer", options={"default" = 0}) **/
    protected $disabled;

}

$ php bin/doctrine orm:schema-tool:update --dump-sql
ALTER TABLE example CHANGE disabled disabled TINYINT(1) DEFAULT '0' NOT NULL;

This alter statement is generated on every run of the schema-tool even though the schema has already been altered.

Originally created by @doctrinebot on GitHub (Nov 9, 2012). Originally assigned to: @beberlei on GitHub. Jira issue originally created by user ccomer: When using the Column annotation on an entity and passing the options parameter to set a default value for a column, the doctrine cli will generate the alter statement every time the schema-tool is run. This doesn't break the functionality of updating the schema using the cli but when you have multiple entities using default values in this manner it becomes cumbersome to investigate issues during updates that fail and you need to dump the generated sql to examine. Use case: We have a number of entities that include 'boolean' flags. The data for these entities is inserted into the database through an integration process handled by another application. For all of the flags we want to set a default value of 0 to avoid having to modify the integration scripts when a new flag is added to an entity and the data is not available yet. Example entity: ``` /**** * @ORM\Entity * @ORM\Table(name="example") */ class Example { /**** * @ORM\Id * @ORM\Column(type="integer") */ protected $id; /*** @ORM\Column(type="integer", options={"default" = 0}) **/ protected $disabled; } ``` ``` $ php bin/doctrine orm:schema-tool:update --dump-sql ALTER TABLE example CHANGE disabled disabled TINYINT(1) DEFAULT '0' NOT NULL; ``` This alter statement is generated on every run of the schema-tool even though the schema has already been altered.

admin added the Bug label 2026-01-22 14:00:36 +01:00

admin closed this issue

2026-01-22 14:00:37 +01:00

admin commented

2026-01-22 14:00:38 +01:00

@doctrinebot commented on GitHub (May 1, 2013):

Comment created by @beberlei:

This is fixed for 2.3.4

@doctrinebot commented on GitHub (May 1, 2013): Comment created by @beberlei: This is fixed for 2.3.4

admin commented

2026-01-22 14:00:39 +01:00

@doctrinebot commented on GitHub (May 1, 2013):

Issue was closed with resolution "Duplicate"

@doctrinebot commented on GitHub (May 1, 2013): Issue was closed with resolution "Duplicate"

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: doctrine/archived-orm#2688