You probably changed a field from type string to type array in your entity but already have data the database. It's failing at trying to convert an empty string from the database to an array.
If it's a development database, simply delete it and create it again, or just delete the offending rows. Or you could convert all the empty strings to a:0:{} (a serialized empty array).
UPDATE table SET column="a:0:{}" WHERE column = "";
I would prefer not having everyone running SQL on their Production Database.
@ORM\Column(type="array", nullable=TRUE)
An easier solution in make the Column nullable, so after you run your "console doctrine:schema:update --force" the existing DB entries will get a NULL value, instead of an empty string. And doctrine can handle a converting the database value NULL to Doctrine Type array. It should be just a NULL array reference. And PHP empty() doesn't care if its zero sized array or NULL.
In MySQL, I get the following sql-dump:
ALTER TABLE my_table ADD my_new_column LONGTEXT DEFAULT NULL COMMENT '(DC2Type:array)'
your db tables column type (eg: longtext) can't match Doctrine's column type. change column type.
You probably changed a field from type string to type array in your entity but already have data the database. It's failing at trying to convert an empty string from the database to an array.
If it's a development database, simply delete it and create it again, or just delete the offending rows. Or you could convert all the empty strings to
a:0:{}
(a serialized empty array).I would prefer not having everyone running SQL on their Production Database.
An easier solution in make the Column nullable, so after you run your "console doctrine:schema:update --force" the existing DB entries will get a NULL value, instead of an empty string. And doctrine can handle a converting the database value NULL to Doctrine Type array. It should be just a NULL array reference. And PHP empty() doesn't care if its zero sized array or NULL.
In MySQL, I get the following sql-dump:
You can add new Type like that: