Development

#4027 ([sfPropelPlugin] Ignore doctrine schemas)

You must first sign up to be able to contribute.

Ticket #4027 (closed defect: fixed)

Opened 6 months ago

Last modified 2 months ago

[sfPropelPlugin] Ignore doctrine schemas

Reported by: francois Assigned to: dwhittle
Priority: minor Milestone: 1.0.18
Component: model Version: 1.1.0
Keywords: Cc:
Qualification: Unreviewed

Description

It is possible to use both Propel and Doctrine in an application, if they use different connection settings. But there is a problem with the propel generator: it looks for schema files under the config/ directory, and consequently finds Doctrine schemas, too. Trying to deal with these schemas, the generator dies.

Propel should ignore those schemas.

Simple patch : add a ->prune('doctrine') in sfPropelBaseTask::schemaToXML() (line 88)

Also, this could be backported to the 1.0 branch in sfPakePropel/_propel_convert_yml_schema().

Change History

07/21/08 08:26:59 changed by dwhittle

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

(In [10374]) sfPropelPlugin: fixed #4027 (ignore doctrine schemas)

09/29/08 17:34:19 changed by francois

Any chance this can be backported to the 1.0 branch? IMHO, it can be considered as a bug, since it prevents the cohabitation of Propel and Doctrine on the same project. Besides, the BC break risk is null...

09/29/08 17:43:14 changed by fabien

(In [11850]) [1.0] ignore doctrine schema in the propel tasks (closes #4027)

09/29/08 17:43:37 changed by fabien

  • milestone set to 1.0.18.

10/02/08 12:23:17 changed by francois

  • status changed from closed to reopened.
  • resolution deleted.

It is now ok in the Propel 1.3 plugin and in the symfony 1.0 branch...

But symfony 1.1 still has a bundled Propel plugin, which has not the fix for it.

11/03/08 09:20:31 changed by dwhittle

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

(In [12594]) 1.1: fixed propel plugin does not ignore doctrine schemas (closes #4027)