Doctrine 1

Duplicate CREATE TABLE entries in schema.sql when using column_inheritance

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.2.1
  • Fix Version/s: None
  • Component/s: Inheritance
  • Labels:
    None
  • Environment:
    MySQL 5 / PHP 5.3.1 / Symfony 1.4.3 (branch) / Doctrine 1.2.1 / Mac OSX

Description

When creating a model involving column_inheritance the CREATE TABLE statement gets duplicated.

The second CREATE TABLE include an index for the keyField.

Test doctrine generated models and generated schema.sql attached.

  1. File
    BaseInherited.class.php
    02/Mar/10 12:38 PM
    0.4 kB
    webPragmatist
  2. File
    BaseInheriter.class.php
    02/Mar/10 12:38 PM
    1 kB
    webPragmatist
  3. File
    schema.sql
    02/Mar/10 12:38 PM
    0.4 kB
    webPragmatist
  4. Text File
    sandbox-console.txt
    02/Mar/10 1:05 PM
    1 kB
    webPragmatist
  5. File
    kerdany_10-11-18-08-30.sql
    18/Nov/10 1:42 AM
    0.6 kB
    Hany el-Kerdany
  6. File
    kerdany_10-11-18-08-30.yml
    18/Nov/10 1:42 AM
    0.4 kB
    Hany el-Kerdany

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
webPragmatist added a comment - - edited

It seems this issue is related to using array_unique() and databases which doctrine creates index along with the CREATE TABLE statement.

This does not occur on sqlite as shown above in the console-log.txt (this db uses the CREATE INDEX statement).

Show
webPragmatist added a comment - - edited It seems this issue is related to using array_unique() and databases which doctrine creates index along with the CREATE TABLE statement. This does not occur on sqlite as shown above in the console-log.txt (this db uses the CREATE INDEX statement).
Hide
Permalink
Svetoslav Shterev added a comment -

Yes, it seems SQL CREATE TABLE statements are generated for each of the children as well, but with sqlite, array_unique() filters out the ones that are "extra".
But the MySQL statements all differ(due to indexes, I don't know if other things can cause them to differ as well), and as such all are left.

Show
Svetoslav Shterev added a comment - Yes, it seems SQL CREATE TABLE statements are generated for each of the children as well, but with sqlite, array_unique() filters out the ones that are "extra". But the MySQL statements all differ(due to indexes, I don't know if other things can cause them to differ as well), and as such all are left.
Hide
Permalink
Tom Boutell added a comment -

We're seeing this issue too. doctrine:build --all --and-load works fine, but doctrine:build-sql generates duplicate CREATE TABLE statements. Our in-house workflow is the former, so the latter came as a surprise. Is there any sign of progress on this one?

Show
Tom Boutell added a comment - We're seeing this issue too. doctrine:build --all --and-load works fine, but doctrine:build-sql generates duplicate CREATE TABLE statements. Our in-house workflow is the former, so the latter came as a surprise. Is there any sign of progress on this one?
Hide
Permalink
Sebastian Schulze added a comment -

This looks like a Duplicate of DC-123.

Show
Sebastian Schulze added a comment - This looks like a Duplicate of DC-123 .
Hide
Permalink
Hany el-Kerdany added a comment -

A little addition to the symptoms of this problem.

If the one of the child classes has a foreign key to another entity, another Third Create table SQL will be created, which contains the an index on the foreign key column.

In other words, it seems that an additional create table statement is created for each automatically created index.

An illustration is in the attached yml and sql schema:
kerdany_10-11-18-08-30.yml
kerdany_10-11-18-08-30.sql

Tom Boutell: doctrine:build --all generates the problem with me!

Show
Hany el-Kerdany added a comment - A little addition to the symptoms of this problem. If the one of the child classes has a foreign key to another entity, another Third Create table SQL will be created, which contains the an index on the foreign key column. In other words, it seems that an additional create table statement is created for each automatically created index. An illustration is in the attached yml and sql schema: kerdany_10-11-18-08-30.yml kerdany_10-11-18-08-30.sql Tom Boutell: doctrine:build --all generates the problem with me!

People

  • Assignee:
    Jonathan H. Wage
    Reporter:
    webPragmatist
Vote (3)
Watch (4)

Dates

  • Created:
    Updated: