Re: Number of formal and actual parameters in a JDOQL query

[Craig L Russell]

I agree. If there are more actual parameters, regardless of whether it's in an array or map, they should be ignored. I'll propose wording for the specification. Craig On Dec 5, 2005, at 5:16 PM, Bin Sun wrote: +1 In some cases a developer tends to preset serveral parameters first in a Map, and choose to use some of them conditionally later in JDOQL. --- Michael Bouschen <[EMAIL PROTECTED]> wrote: Hi, the current spec defines there must be at least as many actual  parameters as there are formal parameters for a JDOQL query (section  14.3: "Each parameter named in the parameter declaration must be bound  to a value when the query is executed."). But the spec does not define  the behavior if there are more actual than formal parameters. I propose  to ignore these parameters. That means, in case of a map any name/value  pair is ignore if the name does not match any implicit or explicit  declared parameter. In case of an array, parameters at index n or higher  are ignore if n is the number of implicit or explicit declared parameters. Regards Michael --  Michael Bouschen [EMAIL PROTECTED] Engineering GmbH mailto:[EMAIL PROTECTED] http://www.tech.spree.de/ Tel.:++49/30/235 520-33 Buelowstr. 66 Fax.:++49/30/2175 2012 D-10783 Berlin __________________________________________  Yahoo! DSL – Something to write home about.  Just $16.99/mo. or less.  dsl.yahoo.com  Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!

smime.p7s
Description: S/MIME cryptographic signature