[_] CakePHP 1.2, ready for production?
Jon Bennett
jmbennett at gmail.com
Tue Mar 18 12:08:16 GMT 2008
Hi Tom, > Yes of course. I think it's down to your personal preference. I'd rather not > be painted in to a corner with my database unless it really is going to save > me a massive amount of time and IMHO cake does not. It's totally unnecessary > to have an auto id field on something that has such a strong candidate key. > It also means I potentially have to join more tables than I need to. from a pure db design perspective sure - but is there really that much harm in having an auto_increment id coupled with a unique index for the username field? A lot of cake's form behaviour is based around either having or not having an ID, by leaving off you're handicapping the framework. I think that's the crux of the issue really, if you want and only ever want to do things your way then a framework will never suit you - if on the other hand you are prepared to overlook small issues like the above and just get on with things, you'll be fine. cheers, jon -- jon bennett w: http://www.jben.net/ iChat (AIM): jbendotnet Skype: jon-bennett