The database diagram is in the Files section of the Google Group, not
the Discussions. http://cake-php.googlegroups.com/web/
projectdata.png is the diagram in question.
As for your questions. It is certainly not necessary to set up any
kind of association between your tables inside the database - you can
do it all in Cake with no problems. Whether there are advantages to
doing so I don't know - databases are not my strong point. I would be
interested to hear from anyone knowledgeable in this - how do database
level associations work, and what are the advantages?
Well, ACL is just access control, and you certainly do want access
control for both your users and your content managers. I haven't used
the standard Cake ACL, but a package like OthAuth will allow you to
define specifics of what actions are permitted. In my own
applications I use my own access control, which basically consists of
a function call to check if an affected row is owned by the current
user (or Operator), ie:
function delete($id){
if ( $this->MyModel->isOperator( $this->current_operator_id, $id )
and $this->MyModel->del($id) ){
// redirect with success message
} else {
// redirect with failure message
}
}
the isOperator function is in my AppModel, and just reads the row in
question and checks the operator_id field. This is of course much
simpler than you may want (where administrators can edit anyone's
data, and groups of users may edit each other's), but it shows there
are a number of methods to check access levels.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
