[DMIG-9] table "contact_attribute" already exists - with mappedSuperClass Created: 25/Oct/10 Updated: 26/Nov/10 Resolved: 26/Nov/10 |
|
| Status: | Resolved |
| Project: | Doctrine Migrations |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Sebastian Hoitz | Assignee: | Jonathan H. Wage |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Description |
|
I have a class App_Model_Contact_Attribute: App_Model_Contact_Attribute:
type: mappedSuperclass
inheritanceType: SINGLE_TABLE
table: contact_attribute
discriminatorColumn:
name: type
type: string
length: 20
columnDefinition: "varchar(20) not null"
discriminatorMap:
emailAddress: App_Model_Contact_EmailAddress
twitterAccount: App_Model_Contact_TwitterAccount
id:
id:
type: integer
columnDefinition: "int unsigned not null auto_increment"
generator:
strategy: AUTO
fields:
value:
type: string
notnull: true
columnDefinition: "varchar(45)"
manyToOne:
contact:
joinColumn:
name: contactID
referencedColumnName: id
columnDefinition: "int not null unsigned"
targetEntity: App_Model_Contact
fetch: EAGER
cascade: [persist]
and a class App_Model_Contact_EmailAddress and App_Model_Contact_TwitterAccount. Both yml files look similar to this: App_Model_Contact_TwitterAccount: type: entity Now, when I want to execute migrations:diff it always fails giving me the message: "Table contact_attribute already exists". This probably has to do with the mappedSuperClass declaration in my models. |
| Comments |
| Comment by Sebastian Hoitz [ 26/Nov/10 ] |
|
This bug does not seem to occur anymore. |