Doctrine 1
  1. Doctrine 1
  2. DC-165

outdated symfony Yaml parser causes troubles

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.0.12, 1.1.4, 1.2.0-ALPHA1
    • Fix Version/s: 1.2.0-BETA1
    • Component/s: File Parser
    • Labels:
      None

      Description

      all doctrine versions use an imported and modified version of sfYaml.
      Either that needs to be changed to an external, or bugfixes need to be ported.
      see this ticket from symfony trac:
      http://trac.symfony-project.org/ticket/7496

      I wanted to use some yaml in a fixture to populate data for the "array"-Fieldtype.

      In the fixture I used:

      items:
        -
          name:           temp_zone_1
          fieldLabel:     Temp. Zone 1 [°C]
          value:          997
          minValue:       0
          maxValue:       3000
      ...
      

      the resulting serialized array in the table array looked like:

      s:5:"items";a:9:{i:0;a:5:{s:4:"name";s:11:"temp_zone_1";s:10:"fieldLabel";s:18:"Temp. Zone 1 [°C]";s:5:"value";s:3:"997";s:8:"minValue";i:0;s:8:"maxValue";s:4:"3000";}...
      

      There you can easily see, that "value" is now a string, "minValue" an integer (why?) and maxValue another string. This went awfully wrong somewhere.

      = Workaround and/or solution =
      I took the current parser from `lib/yaml/sfYamlParser.php` and copied it into the existing Parser in `lib/plugins/sfDoctrinePlugin/lib/vendor/doctrine/Doctrine/Parser/YamlSf/Parser.php`. That fixed the problem.

      == Additional Information ==

      used Version in Symfony 10832 2008-08-13
      used Version in sfDoctrinePlugin 8869 2008-05-09

      HTH,
      Michael

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Jonathan H. Wage
            Reporter:
            Fabian Lange
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: