Uploaded image for project: 'Doctrine 1'
  1. Doctrine 1
  2. DC-418

Inherited models creating NOT NULL restrictions on their parents

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 1.2.1
    • Fix Version/s: None
    • Labels:
      None
    • Environment:
      Linux skywalker-9 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC 2009 x86_64 GNU/Linux

      Description

      to reproduce, create the yaml included in sample.yaml (Note the not-null columns in each subclass)

      if you try to save an OnlineProduct without setting copyright_year, or if you create a print_product without setting website_branding_id, then you will get a not null error.
      Inherited tables should be able to set their own NOT NULL columns without affecting other tables in the inheritance tree (should be handled in the preSave() method? or is there another mechanism?)

        Activity

        Hide
        jlukescott luke scott added a comment -

        YAML format was destroyed during copy & paste!
        I'm attaching the sample yaml, instead of including it in the description

        Show
        jlukescott luke scott added a comment - YAML format was destroyed during copy & paste! I'm attaching the sample yaml, instead of including it in the description

          People

          • Assignee:
            jwage Jonathan H. Wage
            Reporter:
            jlukescott luke scott
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: