John, thank you for the reply. I will follow your suggestion.
Is my approach good? Any other suggestions of how to tackle the
situation I'm describing?
Thanks!
MinaTSU
On May 8, 2:02 am, John Andersen wrote:
> You may consider not making a field "leader", but a field "role", so
> that you can
You may consider not making a field "leader", but a field "role", so
that you can assign possible future roles, that members may play in a
project - example: manager, coder, analyst, designer, technical
writer, etc.
Enjoy,
John
On May 7, 3:59 pm, MinaTSU wrote:
> Hello everybody!
>
> First
Hello everybody!
First post.
CakePHP newb!
Apologies beforehand if this was answered beforehand.
(I did a search with no success).
Here is the problem I'm facing:
I'm designing the database of a new site. The site is to host several
projects. People in order to join projects first have to regis
