opinion I see two possibilities:
1 - not create tables with composite keys. When you need to use
composite keys to identify a record, create one more field with the
name ID and put it as primary key.
2 - forget standardization. Choose one of the fields to put in
$ primaryKey attribute
with composite key.
what did you do? Since CakePHP recognizes only one field to
primaryKey!
In my opinion I see two possibilities:
1 - not create tables with composite keys. When you need to use
composite keys to identify a record, create one more field with the
name ID and put it as primary key
possibilities:
1 - not create tables with composite keys. When you need to use
composite keys to identify a record, create one more field with the
name ID and put it as primary key.
2 - forget standardization. Choose one of the fields to put in
$ primaryKey attribute of the model and when you need
Dear,
Someone must have encountered a situation where a table had
with composite key.
what did you do? Since CakePHP recognizes only one field to
primaryKey!
In my opinion I see two possibilities:
1 - not create tables with composite keys. When you need to use
composite keys to identify
,
Someone must have encountered a situation where a table had
with composite key.
what did you do? Since CakePHP recognizes only one field to
primaryKey!
In my opinion I see two possibilities:
1 - not create tables with composite keys. When you need to use
composite keys to identify a record
