> The patches seem like they would work just fine, but that's just me > looking at them, not having tested them. I'll take it on faith that > they're well tested. However, if you search the Cake core for > 'primaryKey,' you'll find that it is used in many other places, and IMO > changing them all would be pretty cost-prohibitve in terms of time and > effort. Feel free to prove me wrong ;-)
*grin* I'm not sure yet where to start. Moreover because i'm only looking into cakephp for only two weeks now. I was thinking of not actually changing any of the cake core code, but maybe inheriting something and overloading. But that seems pretty tough going. Also I feel my passing of array() keys had to be changed to something more intuitive (then again, cake makes extensive use of arrays). Might be we could abstract (primary) keys away into a class. That way it's possible to change their behaviour & look/feel without touching the core code. Well apart from incorporating the changes to make them classes/objects :) Albert --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
