Re: composite keys to identify a record

2010-04-19 Thread Martin Westin
enan Augusto wrote: > > >>> 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! > > >>

Re: composite keys to identify a record

2010-04-18 Thread Jeremy Burns
red 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

Re: composite keys to identify a record

2010-04-18 Thread j0n4s.h4rtm...@googlemail.com
countered 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 > > com

Re: composite keys to identify a record

2010-04-16 Thread Jeremy Burns
ear, > > 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

2010-04-16 Thread Renan Augusto
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 a