Jira issue originally created by user hexmode:
doctrine:schema:update keeps thinking there is more to do:
$ php app/console doctrine:schema:update --dump-sql
ALTER TABLE Account CHANGE guid guid VARCHAR(255) NOT NULL;
ALTER TABLE Customer CHANGE guid guid VARCHAR(255) NOT NULL, CHANGE authGuid authGuid VARCHAR(255) NOT NULL
$ php app/console doctrine:schema:update --force
Updating database schema...
Database schema updated successfully! "2" queries were executed
Comment created by stof:
Can you paste your ORM mapping for these fields ?
Comment created by jrobeson:
I had the same problem. I used doctrine:mapping:import
to bootstrap some entities. It generated my
session entity primary key with a GeneratedValue strategy of
IDENTITY when it should have been NONE.
This sounds like the same problem with the string key
and incorrect GeneratedValue strategy.
PS: I ran into that doctrine:mapping:import issue
perhaps a year ago, when i first started playing with doctrine.
I do not know if it still persists.
Issue was closed with resolution "Incomplete"