Hello,
I was thinking about the use of integer as primary key of the table or use
a char(36) as UUID in the entire project,
What I dont like about the integer, is the auto increment number, So I
decided to use char(36) 'cause cake automatically fill it with an UUID, but
I dont know if this can
it will slow things down and it will store a lot of overhead data (due
to the byte size of those chars compared to integers).
but if speed isnt that big of an issue you are fine.
it gets problematic in the 1 to 5 record area
everything from then on you will really feel - especially with
Whats the reason for disliking auto-incrementing numbers? Its probably the
best thing about databases.
On Wednesday, February 29, 2012 6:53:38 AM UTC-8, Ighor Martins wrote:
Hello,
I was thinking about the use of integer as primary key of the table or use
a char(36) as UUID in the entire
There is some debate that keys should be meaningful, and I get that - but a
UUID is as meaningless as an auto incremented key.
With judicious use of routes, configuration, and other such bits you can
utterly hide your IDs from public scrunity if that is what you're worried
about... personally I
check out all of the plugins at http://cakedc.github.com all of them are
using UUID
--
Larry E. Masters
On Wed, Feb 29, 2012 at 8:53 AM, Ighor Martins ighor.mart...@gmail.comwrote:
Hello,
I was thinking about the use of integer as primary key of the table or use
a char(36) as UUID in the
Just in case, i'm using UUID as primary key for branch office. periodically
integrated with database in HO.
On Thu, Mar 1, 2012 at 8:37 AM, Larry E. Masters php...@gmail.com wrote:
check out all of the plugins at http://cakedc.github.com all of them are
using UUID
--
Larry E. Masters
On
