Hello, I am trying to build an acl for a module that has to be stored in db. serialize() is not an option because using it means the acl table won't be in 1NF (aggregating complex data in a column); I also implement Zend_Resource_Interface in my Zend_Db_Row subclassings, so serialize() happily stores my entire section table in the field 'acl' of the module row. I am now implementing a db backend while subclassing Zend_Acl that uses some tables in normal forms. However, the foreign key for resources inheriting are a redundancy:
sections (id, id_parent_section, name, ...) acl_resources(id, id_parent_resource, name, type, module) It is possible to avoid redundancy of parent relationship and at the same time to not couple together Zend_Acl extension and the module structure? -- Giorgio Sironi Piccolo Principe & Ossigeno Scripter http://www.sourceforge.net/projects/ossigeno
