Doctrine 1
  1. Doctrine 1
  2. DC-1043

Error:"When using..ATTR_AUTO_ACCESSOR_OVERRIDE you cannot.. name "data" ..." when running doctrine:build-schema ... except I'm NOT using that word

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:
      Mac OSX 10.6.8 running MAMP Pro 2.0.5 with PHP 5.3.6 ... this is a local symfony install which is also using the apostrophe cms.

      Description

      Was able to resolve this - see comment below - but still think it counts as a bug since the source of the error is so unclear

      Hello,
      I'm familiarizing myself with symfony at this point, but doctrine seems like a very accessible ORM tool overall. This install will also use the apostrophe plugin though that is more a client request and it is seeming to complicate a lot of issues from what I can see. Right now, I am just trying to create some db tables in schema.yml and build them with doctrine. When running $ php symfony doctrine:build-schema I get the following error: When using the attribute ATTR_AUTO_ACCESSOR_OVERRIDE you cannot use the field name "data" because it is reserved by Doctrine. You must choose another field name.

      Which would be clear enough except I'm NOT using "data" as a field name in my schema file: here's what I'm using:

      sfTravelLodgingLocationsType:
      columns:
      lodging_name:

      { type: string(255) }

      lodging_code:

      { type: string(255) }

      sfTravelLodgingLocations:
      columns:
      lodging_type_code:

      { type: integer, notnull: true }

      name:

      { type: string(255), notnull: true }

      address:

      { type: string(255), notnull: true }

      city:

      { type: string(255), notnull: true }

      distance:

      { type: integer, notnull: true }

      phone:

      { type: string(255), notnull: true }

      known_2b_sold_out:

      { type: boolean, notnull: true, default: 0 }

      relations:
      Travel_Lodging_LocationsType:

      { local: type_id, foreign: id }

      I'm assuming this is a misnamed error call ... I have found a few references to that same error in other threads but none that resolve it

        Activity

          People

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

            Dates

            • Created:
              Updated: