Doctrine 1

CLONE [DC-558] incorrect handling of MODEL_CLASS_PREFIX causes Doctrine_Migration_Diff to drop the whole database when working from YAML (Regression)

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Critical Critical
  • Resolution: Unresolved
  • Affects Version/s: 1.2.3
  • Fix Version/s: None
  • Component/s: Migrations
  • Labels:
    None
  • Environment:
    Current HEAD of Doctrine 1.2

Description

Replicating the bug:
1. Set ATTR_MODEL_CLASS_PREFIX non-null
2. create schema file with entity
3. run doctrine build-all
4. copy schema file
5. edit schema file to add column to entity
6. run generate-migrations-diff from copy of schema file to edited schema file

Expected (previous) behaviour:
Migration is generated to add the new column to entity

Real behaviour:
Drops entity from database and creates new

  1. File
    dc755TestCase.diff
    30/Aug/10 6:16 PM
    3 kB
    Andrew Coulton
  2. File
    fix755.diff
    30/Aug/10 6:24 PM
    0.6 kB
    Andrew Coulton

Activity

Ascending order - Click to sort in descending order
Andrew Coulton made changes -
Field Original Value New Value
Summary CLONE [DC-558] incorrect handling of MODEL_CLASS_PREFIX causes Doctrine_Migration_Diff to drop the whole database when working from YAML CLONE [DC-558] incorrect handling of MODEL_CLASS_PREFIX causes Doctrine_Migration_Diff to drop the whole database when working from YAML (Regression)
Affects Version/s 1.2.3 [ 10051 ]
Affects Version/s 1.2.0 [ 10043 ]
Affects Version/s 1.2.1 [ 10044 ]
Environment Vanilla sandbox on version 1.2.1 and 1.2.0
both sqlite and mysql, so its not driver dependant 		Current HEAD of Doctrine 1.2
Description Replicating the bug:
1. unzip vanilla sandbox.
2. create schema file with entity
3. run ./doctrine build-all
4. modify schema, add column to entity.
5. run ./doctrine generate-migrations-diff

Expected behaviour:
generates migration wich adds column to entity.

Real behaviour:
Drops entity from database

Similar issue:
http://groups.google.com/group/doctrine-user/browse_thread/thread/8b4a0fc0778a388a/79446784623b8497?lnk=gst&q=1.2.1+migration 		Replicating the bug:
1. Set ATTR_MODEL_CLASS_PREFIX non-null
2. create schema file with entity
3. run doctrine build-all
4. copy schema file
5. edit schema file to add column to entity
6. run generate-migrations-diff from copy of schema file to edited schema file

Expected (previous) behaviour:
Migration is generated to add the new column to entity

Real behaviour:
Drops entity from database and creates new
Priority Minor [ 4 ] Critical [ 2 ]
Fix Version/s 1.2.3 [ 10051 ]
Andrew Coulton made changes -
Attachment dc755TestCase.diff [ 10752 ]
Andrew Coulton made changes -
Attachment fix755.diff [ 10753 ]

People

  • Assignee:
    Jonathan H. Wage
    Reporter:
    Andrew Coulton
Vote (0)
Watch (1)

Dates

  • Created:
    Updated: