Re: Sugestion for next versions

I think you need to spend a bit of time with the good book: http://book.cakephp.org/2.0/en/getting-started/cakephp-conventions.html

> 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.

FWIW - I don't think using one table for all joins (with no reason beyond wanting one table) is a particularly good db design.

Also it would be nice if suggestions came in the form of code including tests (since that also involves looking at the existing code).

Free icecreams would be nice too.

AD

On Tuesday, 18 September 2012 16:02:57 UTC+2, André Luis wrote:

Can be used too, but both cases (uniqid from PHP or uuid from Mysql) we need to change something in our AppModel to have this feature, i am using from PHP because its much smaller string.

Em segunda-feira, 17 de setembro de 2012 17h44min22s UTC-3, AD7six escreveu:

Why would you not use uuids?

AD

--
Like Us on FacekBook https://www.facebook.com/CakePHP
Find us on Twitter http://twitter.com/CakePHP
 
---
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.
Visit this group at http://groups.google.com/group/cake-php?hl=en.