Re: Urgent Help needed: How to Correct this table so it doesn't have Composite Primary Key?

On Dec 28, 3:55 am, John Maxim <goog...@gmail.com> wrote:
> Hi Jeremy, Thanks for your link will definitely look into that.
>
> ~~Continue my question~~
> I was going to ask about using this:http://book.cakephp.org/view/1027/query
>
> There are 2 options if I'm correct based on cookbook 1.3
> ~~
> Rather than using an auto-increment key as the primary key, you may
> also use char(36). Cake will then use a unique 36 character uuid
> (String::uuid) whenever you save a new record using the Model::save
> method.
>
> according to:http://book.cakephp.org/view/903/Model-and-Database-Conventions
> ~~
> What's the advantage of using char(36) ?

A uuid (a 36 char string) is unique - always. It's main purpose is to
be unique, nothing else. Obfuscation is a side effect, not the goal.

They are most relevant with distributed datastores whereby you need to
synchronize data and inserts across multiple servers. An insert on
server A can safely and without concern be replicated to server B
because a row with the same ID cannot exist originating from another
server.

http://en.wikipedia.org/wiki/Universally_unique_identifier

AD

Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions.

You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en