From dev-return-29918-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Mon Apr 06 18:11:48 2009 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 59686 invoked from network); 6 Apr 2009 18:11:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Apr 2009 18:11:48 -0000 Received: (qmail 43668 invoked by uid 500); 6 Apr 2009 18:11:47 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 43601 invoked by uid 500); 6 Apr 2009 18:11:47 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 43593 invoked by uid 99); 6 Apr 2009 18:11:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Apr 2009 18:11:47 +0000 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=HTML_MESSAGE,SPF_PASS,SUBJECT_FUZZY_TION X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of akarasulu@gmail.com designates 74.125.44.29 as permitted sender) Received: from [74.125.44.29] (HELO yx-out-2324.google.com) (74.125.44.29) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Apr 2009 18:11:39 +0000 Received: by yx-out-2324.google.com with SMTP id 8so1592444yxg.55 for ; Mon, 06 Apr 2009 11:11:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=HbBckvcdmGqE9SBkx3Cy59hLF9JnMxACQ5J+RbNc6r4=; b=SrMiVpWBMDWAnjS7pFZ7ii5yX0G+9ato+pZMkJopOK3evLPNgjthrevZoCBWIksUFo p1s9fddN4AZzadmxoZ8s95C2xgecANDZcc3HufOIEYFDGLLDftiOH97saNwo9Rq8R3nP XUBBuIL2AKFt4BLjIanxvAaDiezfz34WTF0fw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Bixz+vldRr5UMm7vu+2f+DioEO2XZX9dGBboAKKTscgv6ydTWbuJyPm+saH4tsEcyJ KRgXy6teGJna0VmLRoozE4iuRovoOuDyIbiAmpeio3MZfMl5//xQU1y+mGN3r1smKO+5 ScjIpW7tcVvTYsWQyd2YXMAYwLjC/sicn4v4k= MIME-Version: 1.0 Received: by 10.150.52.2 with SMTP id z2mr1420320ybz.26.1239041478314; Mon, 06 Apr 2009 11:11:18 -0700 (PDT) In-Reply-To: References: Date: Mon, 6 Apr 2009 14:11:18 -0400 Message-ID: Subject: Re: [ApacheDS] Oracle partition committed to ldif-partition branch From: Alex Karasulu To: Apache Directory Developers List Content-Type: multipart/alternative; boundary=000e0cd6ae8c2d4afd0466e6d325 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd6ae8c2d4afd0466e6d325 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi Andrea, On Mon, Apr 6, 2009 at 1:59 PM, Andrea Gariboldi wrote: > I'll be able to configure the ou=schema partition in this branch? > Cause for now i left it for the future because it was not configurable. > We have these goals in the near future: o combine schema and system areas into one under the ou=system partition o allow users to choose which partition type they like for the system partition The second goal is harder to do considering some of the new problems we're going to have to overcome when keeping configuration and schema data in LDIF files. Remember the question you asked about setting up a configuration area without loading schema or partitions? This is pretty hard to do when some of those attributes need schema information associated with them. Regardless I think we can find a way to solve your problem of swapping in the Oracle partition to get schema info. I don't have all the answers right now but I'm sure we'll find them in time. So maybe this merges back into the trunk before we solve these issues but we can keep working it. Alex > > 2009/4/6, Alex Karasulu : > >> I just committed Andrea's Oracle Partition contribution to the >> ldif-partition branch that was created a couple weeks back. There are >> several reasons for this: >> >> o this branch has a better breakdown of packages >> o some of Andrea's unfortunate workarounds due to poor design will go >> away >> o attached tests can be used to make sure Andreas partition behaves >> appropriately >> o making our way to having partitions separated from large core package >> >> Note that I plan to merge this partition back into the trunk after the >> 1.5.5 release when everything is looking good. The neat thing about this is >> when we're done here in a short while we will have 4 separate partition >> types: >> >> o oracle >> o avl >> o ldif >> o jdbm >> >> That will be pretty cool. >> >> Thanks, >> Alex >> > > --000e0cd6ae8c2d4afd0466e6d325 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Andrea,

On Mon, Apr 6, 2009 at 1:59 PM= , Andrea Gariboldi <andrea.gariboldi@gmail.com> wrote:
I'll be able to configure the ou=3Dschema partition in this branch?
= Cause for now i left it for the future because it was not configurable.
=

We have these goals in the near future:

=A0 o = combine schema and system areas into one under the ou=3Dsystem partition =A0 o allow users to choose which partition type they like for the system p= artition

The second goal is harder to do considering some of the new= problems we're going to have to overcome when keeping configuration an= d schema data in LDIF files.=A0

Remember the question you asked about setting up a configuration area w= ithout loading schema or partitions? This is pretty hard to do when some of= those attributes need schema information associated with them.=A0 Regardle= ss I think we can find a way to solve your problem of swapping in the Oracl= e partition to get schema info.=A0 I don't have all the answers right n= ow but I'm sure we'll find them in time.

So maybe this merges back into the trunk before we solve these issues b= ut we can keep working it.

Alex



2009/4/6, Alex Karasulu <akarasulu@apache.org>:


--000e0cd6ae8c2d4afd0466e6d325--