Doctrine 2 - ORM
  1. Doctrine 2 - ORM
  2. DDC-2308

Naming Strategy for Reverse Engeneering

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Mapping Drivers
    • Security Level: All
    • Labels:
      None

      Description

      Unfortunately DatabaseDriver::getClassNameForTable() is declared as private method, which makes it quite difficult to change the naming strategy for reverse engeneering.

      IMO this sould be declared protected. An even better way would be to extend the interface of the Naming Strategy objects to support the reverse direction:

      classToTableName -> tableToClassName
      propertyToColumnName -> columnToPropertyName.

      This way we would have a consistent name-mapping

        Activity

          People

          • Assignee:
            Benjamin Eberlei
            Reporter:
            Andreas Prucha
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: