Using Multiple Primary Keys in Admin Generator
Sometimes, the table we’re using force us to use multiple primary keys as shown in the schema below (config/schema.yml): connection: propel defaultIdMethod: native package: lib.model classes: State: tableName: state columns: id: { type: varchar, size: 2, primaryKey: true } country_id: { type: varchar, size: 2, primaryKey: true } name: { type: varchar, size: 50, index: …