Changes between Version 6 and Version 7 of Document/Development/Design/LdapBackend

Timestamp:

10/14/08 12:28:36 (5 years ago)

Author:

jgarcia@… (IP: 88.26.177.14)

Comment:

--

Document/Development/Design/LdapBackend

@@ -70 +70 @@
          * SUBSTR neccesary for * (different of ~= operator)
        * Get all of them
-         * ldapsearch -H ldap://localhost -x -s base -b "cn=subschema" "(objectclass=*)" matchingrules
+         * ldapsearch -H !ldap://localhost -x -s base -b "cn=subschema" "(objectclass=*)" matchingrules
          * http://tools.ietf.org/html/rfc2252#section-4.5
      * Syntaxes
        * Get all of them
-         * ldapsearch -H ldap://localhost -x -s base -b "cn=subschema" "(objectclass=*)" ldapsyntaxes
+         * ldapsearch -H !ldap://localhost -x -s base -b "cn=subschema" "(objectclass=*)" ldapsyntaxes
          * http://tools.ietf.org/html/rfc2252#section-6
    * Types supported
@@ -114 +114 @@
     SYNTAX 1.3.6.1.4.1.1466.115.121.1.24
 }}}
- * Every Ebox's Types has a method (see Ldap #2 ) description() with a hash with tuples name => type
- * A function "somewhere" gets a EBox::Type (and a Module and Model name) and generates the attributetype schema definitions
-   * For types that have more than one field (e.g. PortRange) the function generates more than one attributetype
+ * Every Ebox's Types has a method (see Ldap !#2 ) description() with a hash with tuples ''name => type''
+ * A function "somewhere" gets a EBox::Type (and a Module and Model name) and generates the ''attributetype'' schema definitions
+   * For types that have more than one field (e.g. !PortRange) the function generates more than one attributetype
    * Special cases will be:
      * Composite: do nothing
-     * HasMany: No need for declare an attributetype, a hasmany field in a model, means a eboxModel as a may-attribute
+     * !HasMany: No need for declare an attributetype, a hasmany field in a model, means that the foreign !EBoxModel will be as a child of the current Ebox Model (the one which the !HasMany attribute, but this's not concern for the schema generation)
 
 === Ldap !#2 ===