You guys freak me out. I know that CakePHP is a great framework, but if this compound primary key is really that important to you, maybe you should get on the Ruby train. If the framework does not fit your needs, find one that does. I don't see what the big issue is.
It's an incovinience. And it's NOT a trivial thing to implement. I really don't understand this whole thing. Before you started your application, didn't you know this feature wasn't implemented? So why start with CakePHP, then complain that a key feature is missing? As nate said, if you want it, take some time and go for it, but the majority doesn't seem to need it that bad, hence it's not in. On Mon, Feb 25, 2008 at 7:55 AM, Mr-Yellow <[EMAIL PROTECTED]> wrote: > > Um.......... I fixed some bugs today and provided the patch. > > The ticket was deleted. > > So much for "open" source. > > -Ben > > > On Feb 26, 12:37 am, nate <[EMAIL PROTECTED]> wrote: > > On Feb 24, 8:13 pm, Mr-Yellow <[EMAIL PROTECTED]> wrote: > > > > > The responses to tickets relating to this issue in trac usually have > > > "wontfix" and a short non-explainatory note basically saying "piss off > > > and stop asking you don't need this, we know best". > > > > Well, I'm really sorry you read such a demeaning tone into my messages > > on Trac. The fact is, whether we "know best" is not even the point. > > The point is, we make decisions on what to support and what not to > > support based on the driving philosophies of this project, and using > > it essentially necessitates an implicit agreement with those > > philosophies. > > > > The fact is, compound primary keys are really just not requested that > > often. Even if they were, we've decided it's just not something we're > > going to implement, because it adds too much overhead in terms of > > complexity. You can argue about relational theory all you want, it's > > simply irrelevant to the decision-making process here. When it comes > > down to it, supporting multi-column primary keys is just not that > > useful to *me*. Furthermore, not enough people have raised it as an > > issue in order for me to go out of my way for them. > > > > But that's the beauty of Open Source: I as a core developer don't > > *have* to implement a particular feature in order for you to use it. > > If lack of support for compound primary keys is really enough of a > > pain point for you, patch the code! :-) No one's stopping you. Just > > don't expect me to take the extra time out of my life to implement a > > feature which I personally would have no use for, nor likely ever > > will. Not to mention the fact that, again, the needless complexity > > that this would add completely undermines the philosophy of the > > framework. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
