Development

#3545 ([PATCH] Propel inheritance breaks when a table's phpName is camelCased table_name)

You must first sign up to be able to contribute.

Ticket #3545 (closed defect: fixed)

Opened 7 months ago

Last modified 7 months ago

[PATCH] Propel inheritance breaks when a table's phpName is camelCased table_name

Reported by: Kris.Wallsmith Assigned to: fabien
Priority: minor Milestone:
Component: model Version: 1.1.0 DEV
Keywords: Cc:
Qualification: Unreviewed

Description

If a table is named history and the Propel OM class is named History (for example), the sfPropelDatabaseSchema class leaves the phpName implied, which breaks the same class' support of Propel's inheritance model.

This patch addresses this bug by falling back to the camelized table name, if no phpName is present. Test are also included in the patch.

Attachments

propel-inheritance-bug.patch (3.1 kB) - added by Kris.Wallsmith on 05/15/08 00:24:10.

Change History

05/15/08 00:24:10 changed by Kris.Wallsmith

  • attachment propel-inheritance-bug.patch added.

05/15/08 08:44:01 changed by FabianLange

  • status changed from new to closed.
  • resolution set to fixed.

(In [8972]) applied Kris patch to new propel inheritance support, using table name if phpName is not set. fixes #3545