Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type;
        b=V0mZudSRzI5yY8bHCp1r4B7R3Grts6p0AuPyQT7h0Wqy8fiUoVBqJqYImVDG+A3bEPs+wjYt7TW+HXLfYeNsPELbXsqpgKwuvv3Z6XtgHSYC11NB0NN+v1PUIoljoSiZzk5RjUAvLWhxl5qPg0vd+kaIbvILv+m/SQD6ONdiRfc=
Message-ID: <5f211bd50610020310t520624eej292d652bfacb727c@mail.gmail.com>
Date: Mon, 2 Oct 2006 12:10:22 +0200
From: "Thomas Mueller" <thomas.tom.mueller@gmail.com>
To: users@jackrabbit.apache.org
Subject: Re: Comparing an RDBMS to JCR
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_76458_13662880.1159783822877"

------=_Part_76458_13662880.1159783822877
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Behi,

Does it imply that using JCR has a __serious__
> performance penalty compared to direct access to the database via JDBC,
> and
> even using ORM tools such as EJB3?


It depends how you use it. There are faster ways to achieve the same thing:
If you want to add a lot of nodes concurrently, it is probably better to use
different parent nodes. For example, you could use one parent node for each
session. In your example you have used the same child node name
('position'). This is supported ('same name sibling') but IMO should be
avoided for multiple reasons (for example, if you want to access a node by
name). So I suggest you use different node names for the child nodes.

*JCR or any other CMS (?) API


The JCR is the only standardized CMS API as far as I know.

Thomas

------=_Part_76458_13662880.1159783822877--