DDC-506: Schema tool no longer creates AUTO_INCREMENT primary keys in MySQL #5013

doctrinebot opened this Issue Apr 10, 2010 · 3 comments

2 participants


Jira issue originally created by user @hobodave:

A recent update broke the schema generation of all primary keys for my models. The following no longer results in an AUTO_INCREMENT primary key in MySQL.

 * @Entity
 * @Table(name="admin_history")
class AdminHistory
     * @Id
     * @Column(type="integer", name="admin*history*id")
     * @GeneratedValue
    protected $id;

Comment created by romanb:

This might have something to do with the CLI refactorings, too? Otherwise I have no idea where this is coming from since the test suite runs fine against mysql (and it obviously uses generated values a lot).


Comment created by @beberlei:



Issue was closed with resolution "Fixed"

@beberlei beberlei was assigned by doctrinebot Dec 6, 2015
@doctrinebot doctrinebot added this to the 2.0-BETA1 milestone Dec 6, 2015
@doctrinebot doctrinebot closed this Dec 6, 2015
@doctrinebot doctrinebot added the Bug label Dec 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment