Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Received-SPF: pass (athena.apache.org: domain of plinskey@gmail.com designates
 72.14.220.152 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:from:to:in-reply-to:content-type
         :content-transfer-encoding:mime-version:subject:date:references
         :x-mailer;
        b=x049U68ZLo5Sy31EEqROiUsii6q0pCVhjqIoqPftZqo7SRs8pJQPYrlS7vUhc/DoUF
         XLsKXJaGbzw1l6wT9ZTCr2HXCah9rmYuDq9POwIX53T/cfxy0psMyyoE9xVcIT5oDR9T
         E4wSASjE7Pd+kJI1O2JL5EBm33w7/EL2yFuQo=
Message-Id: <4AFC2A9B-FB31-4C76-BB5D-24ADB5AECBDC@gmail.com>
From: Patrick Linskey <plinskey@gmail.com>
To: dev@openjpa.apache.org
In-Reply-To: <4B755808.6040008@apache.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: openjpa.jdbc.QuerySQLCache property
Date: Fri, 12 Feb 2010 09:40:40 -0800
References: <C692E401-E8C7-4195-BCA0-72EE01DE71ED@gmail.com>
 <1265923813904-4557587.post@n2.nabble.com>
 <35801EFA-62B5-4B91-95C6-96E18E5D1BCB@gmail.com>
 <4B755808.6040008@apache.org>

Cool, thanks, committed.

-Patrick

On Feb 12, 2010, at 5:30 AM, Donald Woods wrote:

> The 1.3.x branch and Trunk are open for commits, while 1.0.x and 1.2.x
> require approval from Mike Dick as the release manager.
>
> I took a quick look at the 1507 patch and it looks good to me.
>
>
> -Donald
>
>
> On 2/11/10 10:28 PM, Patrick Linskey wrote:
>> Cool... I think that it might be possible to do some sort of
>> deprecation. I'll take a look one of these days.
>>
>> Meanwhile, how are we committing fixes these days? I've got a fix for
>> OPENJPA-1507; what's the process?
>>
>> -Patrick
>>
>> On Feb 11, 2010, at 1:30 PM, Pinaki Poddar wrote:
>>
>>>
>>> Actually openjpa.jdbc.QuerySQLCache is a poor naming choice. That  
>>> name
>>> openjpa.jdbc.QuerySQLCache originated from a rationale that the  
>>> currently
>>> existing technique is a replacement of a previous implementation.  
>>> But
>>> that
>>> rationale is technically incorrect.
>>>
>>> I had preferred and proposed a more appropriate name such as
>>> openjpa.PreparedQueryCache (without any jdbc reference to the name  
>>> --
>>> because technically the current implementation is a kernel-aware
>>> artifact --
>>> with a JDBC specific implementation). But I had not been able to  
>>> find a
>>> solution without replacing/removing the previous implementation
>>> altogether,
>>> and hence to concede that poor naming suggestion. Caching
>>> technique/stratgey
>>> used for the latest implementation is so very different than the  
>>> previous
>>> one that considering it as replacement will be a factual error.
>>>
>>>
>>>
>>>
>>>
>>> -----
>>> Pinaki
>>> -- 
>>> View this message in context:
>>> http://n2.nabble.com/openjpa-jdbc-QuerySQLCache-property-tp4556392p4557587.html
>>>
>>> Sent from the OpenJPA Developers mailing list archive at Nabble.com.
>>

-- 
Patrick Linskey
202 669 5907