Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 30993 invoked from network); 27 Apr 2007 15:00:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Apr 2007 15:00:28 -0000 Received: (qmail 4424 invoked by uid 500); 27 Apr 2007 15:00:33 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 4401 invoked by uid 500); 27 Apr 2007 15:00:33 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 4392 invoked by uid 99); 27 Apr 2007 15:00:33 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Apr 2007 08:00:33 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of stefan.kurla@gmail.com designates 64.233.166.181 as permitted sender) Received: from [64.233.166.181] (HELO py-out-1112.google.com) (64.233.166.181) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Apr 2007 08:00:26 -0700 Received: by py-out-1112.google.com with SMTP id h31so1323150pyc for ; Fri, 27 Apr 2007 08:00:05 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ZOY0dTAVgnG1qgI2lCKfV83Tw2XjGHI/DGAMqbVutplGgaBxWcert16R9Hr/FwNr26mQyfF8qIr1r3dn3m2Z388UlvbGgzG5csabtuRh7S+AsVqWaVwSpCvqyV38xr1CQYjkzf1jNbFZM8I1SpFWynNSBXeh8o5cPbt5i00cnUc= 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:content-transfer-encoding:content-disposition:references; b=GYD2vzQU1TMdQdRWKGX/qEMg7mPPqI1hy3VrZdyEorwmf+TQlLz9r2Ggh+FBgupZloYHUpf+FN1NBdpmFTy/Baj+PCrLtjywXjLYL4mXjRVEZsEAthn4kwHE31l8c5WD6/3MRoAWYQJ5UatG+tHctwQWdu6gX7TuPZHGWMjsYAE= Received: by 10.65.81.10 with SMTP id i10mr6792735qbl.1177686005445; Fri, 27 Apr 2007 08:00:05 -0700 (PDT) Received: by 10.65.75.18 with HTTP; Fri, 27 Apr 2007 08:00:05 -0700 (PDT) Message-ID: <86d42bef0704270800v6e971594s5f5d5887aab46511@mail.gmail.com> Date: Fri, 27 Apr 2007 10:00:05 -0500 From: "Stefan Kurla" To: dev@jackrabbit.apache.org Subject: Fwd: understanding jackrabbit datastorage In-Reply-To: <86d42bef0704261229g33be5acev89604d0e3825bda6@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <86d42bef0704261229g33be5acev89604d0e3825bda6@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org I guess this is more suited for the dev list. Also, I could figure this out by tracing the code, but I would appreciate if someone who has already worked on this could explain. Would help in understanding the system a little bit better and save a little bit time. How is the data actually stored in jackrabbit say using mysql for example and we are just using the default workspace. Say the structure is / --folderA:nt:folder (propertyX:references fileB) ----fileA:nt:file --fileB:nt:file There is the default_binval which has binval_id and binval_data. ### Is this table used to store binary data, where binval_id is the uuid of the jcr:content that this is referring to and binval_data is the actual bytestream blob data There is default_node which has node_id and node_data. ###How is this used? default_prop with prop_id and prop_data ###How is this used? default_refs with node_id and refs_data ###How is this used? My question then is how would the database store the uuids or nodes of the structure that is defined above. Very simple structure but to understand how this structure is actually translated to be stored in the database would be helpful. Thanks.