jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Waschkowski" <mwaschkow...@gmail.com>
Subject Re: 3.1.3.1 Removing Items
Date Fri, 17 Aug 2007 21:16:16 GMT
Thanks for the clarification on redundancy when using node types Marcel. I
was only referring to (for that part of the discussion) to the use of
unstructured nodes.

Have a good weekend,

Mark

On 8/17/07, Marcel Reutegger <marcel.reutegger@gmx.net> wrote:
>
> Mark Waschkowski wrote:
> > In an SQL system, the
> > definition is done once, but each row relates to the original
> definition. In
> > JCR, many contacts  have to redundantly repeat the definition
> information
> > for each node!
>
> This is not quite correct. There is no redundancy in JCR. Each item
> instance in
> JCR always refers to one definition, which is located in the node type
> manager.
> A JCR definition is different from a SQL 'definition' that it also allows
> residual definitions. in that case the name of the item is not prescribed
> by the
> definition. In SQL that's not possible. A column always has a fixed name.
> When
> you manipulate content you are tied to the set of columns in the table.
>
> > Obviously, this is because a node (not considering nodes
> > types for now) is unstructured and could potentially contain any number
> of
> > properties.
>
> Content in JCR can be both structured and unstructured. One is not forced
> to use
> unstructured nodes.
>
> regards
>   marcel
>



-- 
Best,

Mark Waschkowski

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message