Thanks a lot AD. I will have a look to the mysql ref. Yes i can have some tables with more records than a UINT_MAX. It's very challenging, and if you ever heard about "credit check" you have an idea about volume. I will be my first one using cake (and first one too).. (I cross fingers).
Thanks On Jun 13, 6:47 pm, AD7six <[EMAIL PROTECTED]> wrote: > On Jun 13, 6:28 pm, francky06l <[EMAIL PROTECTED]> wrote: > > > Hello, > > > I am in a case study for a quite large/huge application and I love > > cake. I am starting working on 1.2 now and I do not see any problem > > having id's as BIGINT into the DB. > > Am I right to think this knowing that I haven't made complex tests > > neither loaded such volume that would required a bigint ? > > > Thanks > > If you are really going to have a table with more than 4294967295 > rows, they why not. > > an alternative I have seen before is to use a base62 (09A-Za-z) > sequence for assigining primary keys, the equivalent of a maximum INT > value would be "4gfFC3" (6chrs instead of 10). > > Don't think there is any significant advantage one way or the other, > but I could be wrong ;). > > hth, > > AD > PS. Yes, I assumed mysql if that makes a differnce > ref:http://dev.mysql.com/doc/refman/5.0/en/numeric-types.html --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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 -~----------~----~----~----~------~----~------~--~---
