DDC-768: Annotation mapping of type "array" creating a LONGTEXT column... #945

Closed
opened 2026-01-22 12:56:47 +01:00 by admin · 3 comments
Owner

Originally created by @doctrinebot on GitHub (Aug 25, 2010).

Jira issue originally created by user omega:

I have a property on my entity described as follows:

/****
* @Column(type="array")
*/
public $assets;

When I initialize my schema for the first time, it initializes as the MySQL "LONGTEXT" type.

Subsequent calls to:

"$schemaTool->getUpdateSchemaSql($em->getMetadataFactory()->getAllMetadata());"

...insist on making the following change to the database:

"ALTER TABLE Page CHANGE assets assets LONGTEXT NOT NULL"

Even though from what I can tell, the column is already of that type and configuration.

Let me know if any further details are required!

Originally created by @doctrinebot on GitHub (Aug 25, 2010). Jira issue originally created by user omega: I have a property on my entity described as follows: ``` /**** * @Column(type="array") */ public $assets; ``` When I initialize my schema for the first time, it initializes as the MySQL "LONGTEXT" type. Subsequent calls to: "$schemaTool->getUpdateSchemaSql($em->getMetadataFactory()->getAllMetadata());" ...insist on making the following change to the database: "ALTER TABLE Page CHANGE assets assets LONGTEXT NOT NULL" Even though from what I can tell, the column is already of that type and configuration. Let me know if any further details are required!
admin added the Bug label 2026-01-22 12:56:47 +01:00
admin closed this issue 2026-01-22 12:56:49 +01:00
Author
Owner

@doctrinebot commented on GitHub (Aug 26, 2010):

Comment created by @beberlei:

This is a known issue that cannot be fixed (yet), see DBAL-27.

DBAL-42 might allow a fix for this.

@doctrinebot commented on GitHub (Aug 26, 2010): Comment created by @beberlei: This is a known issue that cannot be fixed (yet), see [DBAL-27](http://www.doctrine-project.org/jira/browse/DBAL-27). [DBAL-42](http://www.doctrine-project.org/jira/browse/DBAL-42) might allow a fix for this.
Author
Owner

@doctrinebot commented on GitHub (Aug 26, 2010):

Issue was closed with resolution "Duplicate"

@doctrinebot commented on GitHub (Aug 26, 2010): Issue was closed with resolution "Duplicate"
Author
Owner

@doctrinebot commented on GitHub (Aug 26, 2010):

Comment created by omega:

Hopefully the priority is bumped up a little. This is the second issue that's resulting in Doctrine mis-judging the current state of my schema:

http://www.doctrine-project.org/jira/browse/DDC-755

At present, I have no real way of being able to tell if the schema is correct or not, I can only force an update in the hopes that the correct schema is initialized.

@doctrinebot commented on GitHub (Aug 26, 2010): Comment created by omega: Hopefully the priority is bumped up a little. This is the second issue that's resulting in Doctrine mis-judging the current state of my schema: http://www.doctrine-project.org/jira/browse/[DDC-755](http://www.doctrine-project.org/jira/browse/DDC-755) At present, I have no real way of being able to tell if the schema is correct or not, I can only force an update in the hopes that the correct schema is initialized.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#945