StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POSymfony 1.4/doctrine/sfGuard schema.yml Using sfDoctringGuardPlugin's sfGuardGroup table in a many to many relation
text
Body
copied!<p>am using the sfGuardPlugin and especially the sfGuardGroup table that am using in a many-to-many relation with a "monitor" table (the many to many table is called ALERT): here is my schema.yml:</p> <pre><code>Monitor: tableName: monitor actAs: Timestampable: ~ columns: id : {type: integer(4), primary: true, autoincrement: true} label: {type: string(45)} url: {type: string(80)} frequency: {type: integer} timeout: {type: integer} method: {type: enum, values: [GET, POST]} parameters: {type: string(255)} Groups: class: Groups local: monitor_id foreign: groups_id refClass: Alert Groups: inheritance: extends: sfGuardGroup type: simple relations: Monitor: class: Groups local: id foreign: monitor_id refClass: Alert Alert: actAs: Timestampable: ~ columns: monitor_id: { type: integer(4), primary: true } groups_id: { type: integer, primary: true } relations: Monitor: foreignAlias: GroupMonitors sfGuardGroup: foreignAlias: GroupMonitors </code></pre> <p>when building all the thigs i get this error :</p> <pre><code> SQLSTATE[42000]: Syntax error or access violation: 1072 Key column 'sf_guard_g roup_id' doesn't exist in table. Failing Query: "CREATE TABLE alert (monitor_id INT, groups_id BIGINT, created_at DATETIME NOT NULL, updated_at DATETIME NOT NUL L, INDEX sf_guard_group_id_idx (sf_guard_group_id), INDEX id_idx (id), PRIMARY K EY(monitor_id, groups_id)) ENGINE = INNODB". Failing Query: CREATE TABLE alert ( monitor_id INT, groups_id BIGINT, created_at DATETIME NOT NULL, updated_at DATET IME NOT NULL, INDEX sf_guard_group_id_idx (sf_guard_group_id), INDEX id_idx (id) , PRIMARY KEY(monitor_id, groups_id)) ENGINE = INNODB </code></pre> <p>Any ideas out there?</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload