From dev-return-19093-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Fri May 13 18:19:46 2011 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 E37AF49F6 for ; Fri, 13 May 2011 18:19:45 +0000 (UTC) Received: (qmail 86122 invoked by uid 500); 13 May 2011 18:19:18 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 86002 invoked by uid 500); 13 May 2011 18:19:18 -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 85954 invoked by uid 99); 13 May 2011 18:19:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 May 2011 18:19:18 +0000 X-ASF-Spam-Status: No, hits=2.9 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [212.227.126.171] (HELO moutng.kundenserver.de) (212.227.126.171) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 May 2011 18:19:10 +0000 Received: from [192.168.0.134] (p5B3C5537.dip.t-dialin.net [91.60.85.55]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0MZOYv-1PziGo3JCn-00LwUY; Fri, 13 May 2011 20:18:48 +0200 In-Reply-To: <89453010.10630.1305306887429.JavaMail.tomcat@hel.zones.apache.org> To: dev@openjpa.apache.org Subject: Re: [jira] [Created] (OPENJPA-1999) Optional support for non-sequential positional parameters MIME-Version: 1.0 X-Mailer: Lotus Notes Build V70_M6_06302005 Beta 4 June 30, 2005 Message-ID: From: info@dvholten.de Date: Fri, 13 May 2011 20:18:37 +0200 X-MIMETrack: Serialize by Notes Client on dvh/dvh(Build V70_M6_06302005 Beta 4|June 30, 2005) at 13.05.2011 20:18:44, Serialize complete at 13.05.2011 20:18:44 Content-Type: multipart/alternative; boundary="=_alternative 00649504C125788F_=" X-Provags-ID: V02:K0:zoDPk2ZQxWwI1ZpVC6r6Q9ZzW7HzcnTkuELppzpmFuK 9yybxxw/Ag3bnjK6ggHgMoT1LZI7L4Xei7urwIzpdJnX0oF2V6 Kf0wPtbQcDqUXr3UWcIPi4bOsPK9USHLMz0wRt9g6V2Q/90yV4 8h4DcRWX4w5wDpLFcqC1E/E3ETd3LqN1xJoMNf/XwNLCkHIwGh K90tAfuhwLnHchPYLRfuqgkj1iy3HNRrBZmme9YoXo= --=_alternative 00649504C125788F_= Content-Type: text/plain; charset="US-ASCII" hi folks, i am just following the discussion about the positional parameters. isnt it possible to think about positional parameters just as 'named-by-numbers' parameters? when its possible to use q.setParameter( "x", something ) and q.setParameter( "y", anotherthing ) then i ( without smoking too many mushrooms ) can imagine that the 2 in q.setParameter( 2, whatever ) is very similar to "2". So, the parameter index is not like an array-index, but like a key in a map. when you can handle named parameters, non-sequential index parameters shouldnt be too difficult .. - technically - what the standard says might another thing. hth dvh --=_alternative 00649504C125788F_=--