Thanks. I definitely want to go down the 'less cumbersome' road.
On Jul 14, 1:43 am, "Dardo Sordi Bogado" <[EMAIL PROTECTED]> wrote:
> > Absolute noob here. I have a question about cakePhp database
> > convention. From my understanding of the manual, every table requires
> > a single attribute primary key.
>
> > So, in a table where you might normally have a composite key with two
> > attributes, you should add an 'artificial identifier' as a single-
> > attribute primary key for each tuple, and use that rather than the
> > composite key.
>
> > Firstly, have I got that right?
>
> Yes, you got that right. For some people it sounds dirty but it
> simplifies things a lot.
>
> > Secondly, do people tend to use AUTO INCREMENT a lot to implement such
> > functionality in their databases?
>
> And yes again for the same reason. But it's no mandatory, you can set
> the keys on your own and make your development more cumbersome.
>
> Also UUIDS are supported (and are great) as primary keys, you can set
> the primary key to be char(36) and cake will take care of
> it:http://book.cakephp.org/complete/3/the-manual
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
