You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by Michael Bouschen <mb...@spree.de> on 2005/09/08 16:30:53 UTC
New query assertions
Hi Michelle,
I think we need a new assertion in the query chapter. It is about
overriding elements of a Query instance created using a single string
JDOQL query.
The new assertion A14.6-23 should cover the second and third item in the
bulleted list in section "14.6 Query Interface", subsection "Query
evaluation" on page 147 of the proposed final draft (August 10) of the spec:
• the single string query is first parsed to yield the result, result
class, filter, variable list, parameter list, import list, grouping,
ordering, and range.
• then, the values specified in APIs setResult, setResultClass,
setFilter, declareVariables, declareParamters, declareImports,
setGrouping, setOrdering, and setRange override the corresponding
settings from the single string query.
What do you think?
Regards Michael
--
Michael Bouschen Tech@Spree Engineering GmbH
mailto:mbo.tech@spree.de http://www.tech.spree.de/
Tel.:++49/30/235 520-33 Buelowstr. 66
Fax.:++49/30/2175 2012 D-10783 Berlin
Re: New query assertions
Posted by Michael Bouschen <mb...@spree.de>.
Hi Michelle,
thanks!
Regards Michael
> Hi Michael,
>
> Sounds good. I've added this assertion to the working draft of the spec
> and the spreadsheet.
>
> -- Michelle
>
> Michael Bouschen wrote:
>
>> Hi Michelle,
>>
>> I think we need a new assertion in the query chapter. It is about
>> overriding elements of a Query instance created using a single string
>> JDOQL query.
>>
>> The new assertion A14.6-23 should cover the second and third item in
>> the bulleted list in section "14.6 Query Interface", subsection "Query
>> evaluation" on page 147 of the proposed final draft (August 10) of the
>> spec:
>> • the single string query is first parsed to yield the result, result
>> class, filter, variable list, parameter list, import list, grouping,
>> ordering, and range.
>> • then, the values specified in APIs setResult, setResultClass,
>> setFilter, declareVariables, declareParamters, declareImports,
>> setGrouping, setOrdering, and setRange override the corresponding
>> settings from the single string query.
>>
>> What do you think?
>>
>> Regards Michael
>>
--
Michael Bouschen Tech@Spree Engineering GmbH
mailto:mbo.tech@spree.de http://www.tech.spree.de/
Tel.:++49/30/235 520-33 Buelowstr. 66
Fax.:++49/30/2175 2012 D-10783 Berlin
Re: New query assertions
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi Michael,
Sounds good. I've added this assertion to the working draft of the spec
and the spreadsheet.
-- Michelle
Michael Bouschen wrote:
> Hi Michelle,
>
> I think we need a new assertion in the query chapter. It is about
> overriding elements of a Query instance created using a single string
> JDOQL query.
>
> The new assertion A14.6-23 should cover the second and third item in
> the bulleted list in section "14.6 Query Interface", subsection "Query
> evaluation" on page 147 of the proposed final draft (August 10) of the
> spec:
> • the single string query is first parsed to yield the result, result
> class, filter, variable list, parameter list, import list, grouping,
> ordering, and range.
> • then, the values specified in APIs setResult, setResultClass,
> setFilter, declareVariables, declareParamters, declareImports,
> setGrouping, setOrdering, and setRange override the corresponding
> settings from the single string query.
>
> What do you think?
>
> Regards Michael
>