From dev-return-21300-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Wed Nov 21 17:39:59 2012 Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 66403DCE5 for ; Wed, 21 Nov 2012 17:39:59 +0000 (UTC) Received: (qmail 39025 invoked by uid 500); 21 Nov 2012 17:39:59 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 38991 invoked by uid 500); 21 Nov 2012 17:39:59 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 38980 invoked by uid 99); 21 Nov 2012 17:39:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Nov 2012 17:39:59 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [216.139.250.139] (HELO joe.nabble.com) (216.139.250.139) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Nov 2012 17:39:53 +0000 Received: from jim.nabble.com ([192.168.236.80]) by joe.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TbEGq-0004xW-Kv for dev@openjpa.apache.org; Wed, 21 Nov 2012 09:39:32 -0800 Date: Wed, 21 Nov 2012 09:39:32 -0800 (PST) From: Pinaki Poddar To: dev@openjpa.apache.org Message-ID: <1353519572546-7581892.post@n2.nabble.com> In-Reply-To: <52D48DA6-9705-40E6-980D-815AD0A22495@gmail.com> References: <52D48DA6-9705-40E6-980D-815AD0A22495@gmail.com> Subject: Re: working with slices MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hello Fabio, Slice, by default, expects that each slice has identical schema. In your case seems to deviate from that assumption. One suggestion would be to set a hint "openjpa.hint.slice.Target" [1] to confine the delete operation to e executed in the slice of your choice. [1] http://openjpa.apache.org/builds/2.2.0/apache-openjpa/docs/manual.html#d5e16664 ----- Pinaki Poddar Chair, Apache OpenJPA Project -- View this message in context: http://openjpa.208410.n2.nabble.com/working-with-slices-tp7581693p7581892.html Sent from the OpenJPA Developers mailing list archive at Nabble.com.