Doctrine 2 - ORM

another incorrect mapping not detected by orm:validate-schema

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 2.1.1
  • Fix Version/s: 2.2
  • Component/s: Mapping Drivers
  • Labels:
    None
  • Environment:
    Linux Debian Squeeze, MySQL

Description

Several lines like this one:

<field name="upgrades" type="int" column="Upgrades"/>

Were not flagged by orm:validate-schema as incorrect. Updating a related entity revealed the problem ("int" not being a proper type) at runtime.

Bug: orm:validate-schema should throw an error on incorrect column type.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Benjamin Eberlei added a comment -

Keep it coming, very valuable

Show
Benjamin Eberlei added a comment - Keep it coming, very valuable
Hide
Permalink
Benjamin Eberlei added a comment -

Fixed, but referenced with wrong ticket in master right now.

Show
Benjamin Eberlei added a comment - Fixed, but referenced with wrong ticket in master right now.

People

  • Assignee:
    Benjamin Eberlei
    Reporter:
    Tom Vogt
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: