When using the peer_method parameter in generator.yml with
'doSelectJoinXXX' I get a PropelException? because of ambiguous column names.
generator:
class: sfPropelAdminGenerator
param:
model_class: Entry
theme: default
list:
display: [id, member_id, instrument_id]
sort: [id, desc]
max_per_page: 50
peer_method: doSelectJoinAll
[wrapped: Could not execute query [Native Error: Column 'id' in order
clause is ambiguous] [User Info: SELECT ml_entry.ID, ml_entry.MEMBER_ID,
ml_entry.INSTRUMENT_ID, ml_entry.OFFERS_PRIVATE_LESSONS,
ml_entry.OFFERS_GROUP_LESSONS, ml_entry.TEACHES_AT_HOME,
ml_entry.MINIMUM_DURATION_ID, ml_entry.PLACES, ml_entry.CREATED_AT,
ml_entry.UPDATED_AT, ml_member.ID, ml_member.EMAIL,
ml_member.FIRST_NAME, ml_member.NAME, ml_member.ADDRESS_ID,
ml_member.STREET, ml_member.ZIP_CODE, ml_member.CITY,
ml_member.COUNTRY_ID, ml_member.PHONE, ml_member.CELLPHONE,
ml_member.FAX, ml_member.SHOW_STREET, ml_member.SHOW_PHONE,
ml_member.SHOW_FAX, ml_member.HOMEPAGE, ml_member.FURTHER_INFORMATION,
ml_member.OFFERS_INTRODUCTORY_COURSE, ml_member.TEACHES_NATIONWIDE,
ml_member.PASSWORD, ml_member.LAST_LOGIN_AT, ml_member.CREATED_AT,
ml_member.UPDATED_AT, ml_member.ACTIVATION_KEY, ml_member.TITLE_ID,
ml_instrument.ID, ml_instrument.NAME, ml_instrument.CATEGORY_ID FROM
(ml_entry, ml_member, ml_instrument) WHERE
ml_entry.MEMBER_ID=ml_member.ID AND
ml_entry.INSTRUMENT_ID=ml_instrument.ID ORDER BY `id` DESC LIMIT 50]]
It looks like the ORDER BY clause is wrongly generated, missing the appropriate table prefix.
