Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of mwaschkowski@gmail.com
 designates 64.233.166.181 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=VJZ+COfwWIRsodlaOCU8y4Lnn0bilY9QS9olvp4Fl64ZkcsTrJLSiHq3QslMuKuU13kAGJIXtyytN6R/YGr0lHeUxbdvJ9LcrGsCU6CpO5gyHNI4Sld+g8JxE58dgkeKB1H4JnV2iSqPnzS7HWuLL4fshFfJp/8jNkAP0EH1/Is=
Message-ID: <76a6ebd00708171416na378fbal112d60357d3e5c3a@mail.gmail.com>
Date: Fri, 17 Aug 2007 17:16:16 -0400
From: "Mark Waschkowski" <mwaschkowski@gmail.com>
To: users@jackrabbit.apache.org
Subject: Re: 3.1.3.1 Removing Items
In-Reply-To: <46C5B003.40309@gmx.net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_61149_6005471.1187385376557"
References: <469F7E7C.4090906@yourmail.com>
	 <8641fd7c0707231459r1bf19d64x4e6e42eaa4403819@mail.gmail.com>
	 <76a6ebd00707231821s6c6b9180w800b97500e9890fd@mail.gmail.com>
	 <8641fd7c0707232224g55e3dc00l9724f802a0c600da@mail.gmail.com>
	 <5f211bd50707240013k44dcb6b3p140589d15723116f@mail.gmail.com>
	 <46C088A1.6040506@nuxeo.com>
	 <76a6ebd00708140742o477534a9mdbcc6deaf8ae5b15@mail.gmail.com>
	 <5f211bd50708140755t1a50d2c0nc65bf6ba56de1842@mail.gmail.com>
	 <76a6ebd00708150917y7e713e68uc52edf6dce0c0e83@mail.gmail.com>
	 <46C5B003.40309@gmx.net>

------=_Part_61149_6005471.1187385376557
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

------=_Part_61149_6005471.1187385376557--