db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Craig L Russell <Craig.Russ...@Sun.COM>
Subject Re: Named queries
Date Fri, 21 Oct 2005 00:19:42 GMT
Hi Michael,

Actually, we decided that setUnmodifiable should not take an  
argument, sort of like setRollbackOnly. You can only set unmodifiable  
to true...

Craig

On Oct 20, 2005, at 4:24 AM, Michael Bouschen wrote:

> Hi Michael,
>
> the unmodifiable attribute in the metadata corresponds to methods
> is/setUnmodifiable in the Query API, meaning setting the unmodifiable
> attribute in the metadata is equivalent to calling setUnmodifiable 
> (true)
> on the Query instance created for the named query.
>
> The assertion refers to query instances where the unmodifiable flag is
> false. This makes sure that you can call any setXXX or declareXXX  
> method
> on a query instance created for a named query.
>
> Regards Michael
>
>
>> Hi Craig,
>>
>> assertion A14.5-15 specifies:
>>
>> "The Query instance returned from this method can be modified by the
>> application, just like any other Query instance."
>>
>> The metadata for named queries might contain a boolean attribute
>> "unmodifiable". In cases where that attribute is "true", is that
>> assertion still valid?
>>
>> Regards,
>> Michael
>> --
>> -------------------------------------------------------------------
>> Michael Watzek                  Tech@Spree Engineering GmbH
>> mailto:mwa.tech@spree.de        Buelowstr. 66
>> Tel.:  ++49/30/235 520 36       10783 Berlin - Germany
>> Fax.:  ++49/30/217 520 12       http://www.spree.de/
>> -------------------------------------------------------------------
>>
>>
>
>
> -- 
> 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
>
>


Mime
View raw message