[PATCH] typo in sfPropelData?

Kris, can you do me a favor and check if it works for you even when removing the primary key from that line at all. I think the main point is that it searches for FKs that relate to a different Table. it shouldnt matter if it is part of a pk or not (in m2m it should at max be part of a composite key). Yoour not("!") prevents it being part of a composite PK, but I guess its much better than the column being a PK, which would not work at all.

yep, just checked with the functional tests from fabien. His schema is

  <table name="author_article">
    <column name="author_id" type="integer" primaryKey="true" />
    <foreign-key foreignTable="author">
      <reference local="author_id" foreign="id" />
    </foreign-key>
    <column name="article_id" type="integer" primaryKey="true" />
    <foreign-key foreignTable="article">
      <reference local="article_id" foreign="id" />
    </foreign-key>
  </table>

so there is a composite PK that contains both FKs, using your proposad patch fails this test. I assume you have similar schema, but the FKs are not part of the PK, which is most likely a separate column with an autoincrement id. Simply removing the PK check fixes the issue and seems to make sense for me. It shouldnt matter if its PK or not. It just has to be a FK that related to the other table

(In [9906]) 1.1: fixed m2m propel data loading. fixes #3730

I see. I hadn't considered a mutli-column PK. Thanks for the commit!