On Feb 25, 12:08 pm, avairet <[EMAIL PROTECTED]> wrote:
> - I'm using CakePHP even if I must rewrite a lot of my tables and
> relations in my database schemas, because like you say it has many
> other useful functionnalities!

Great, I hope you find that it's worth it.

> - I'm not enough "master" with it to develop myself this feature, but
> in some months, why not?

Sure, I'm sure there are a few people will find this useful.  Open
Source is all about scratching your own itch.

> - I've just said that will be a good idea to implement it in the
> future releases, to improve the quality of framework.

I'd tend to disagree that supporting composite primary keys in the
core would improve the quality of the framework.  There are many
reasons for this, not the least of which is that there are many
features not directly related to the database that rely on a single
authoritative key to reference a record, so all that functionality is
working against the idea of having a multi-column key.  As always,
feel free to prove me wrong.  If you can find an elegant way to solve
all those issues, then I'm sure I'll be all for it.

> - I understand it's hard for you to always repeat the same thing, but
> keep cool with new members of community, because this problematic is
> not written on documentation/manual/API

I'll make sure that a note gets into the manual regarding our lack of
support for multi-column keys.

Thanks for your input.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to