MMBase

Kees Jongenburger added a comment - 1970-01-01 00:59 otype is not to be defined in object.xml Otype is not to be defined in object.xml. otype is a low level system field alternavie storage implementations are not required to have an otype field

Michiel Meeuwissen added a comment - 1970-01-01 00:59 You can however do it. It breaks otherwise nothing, and you can in this way also make it a searchable field for the editors. I just tried that, and forgot to switch it off, seemingly unrelated things should not break then.

Michiel Meeuwissen added a comment - 2004-06-01 17:32 If you define otype as a not-null NODE field (in object.xml) then you cannot import NODE fields any more. It can be nice to define otype in object.xml, e.g. like this:     <field>       <descriptions>         <description xml:lang="en">           The type of an object.         </description>       </descriptions>       <gui>         <guiname xml:lang="en">Object type</guiname>         <guiname xml:lang="nl">Object-type</guiname>         <guiname xml:lang="eo">Objecttipo</guiname>         <guitype>typedef</guitype>       </gui>       <editor>         <positions>           <input>-1</input>           <list>-1</list>           <search>102</search>         </positions>       </editor>       <db>         <name>otype</name>         <type state="persistent" notnull="true" key="false">NODE</type>       </db>     </field> But then on deploy of e.g. cloud context security: 17:24:09,270 ERR 12063 kb mmbase.module.tools.MMAdmin error.2378 - Insert of node prefix='',otype=9:'-1',owner=1:'admin',name=1:'mmbaseusers',number=9:'-1' failed. Field 'otype' with type NODE is not allowed  to have a null value. The referenced node is not found. Try to reorder the nodes so the referenced node is imported before this one.