The way to go here is to create a Jira and attach a patch with unit tests.
Gary
On Fri, Sep 5, 2014 at 1:01 PM, Alex wrote:
> Hello,
> It is pretty convenient to work with queries in a sql file: it can be
> loaded into SQL client (e.g. SQuirrel) and queries can be tested by by
> selecting/run
Hello,
It is pretty convenient to work with queries in a sql file: it can be
loaded into SQL client (e.g. SQuirrel) and queries can be tested by by
selecting/running them; you get SQL syntax highlighting and you can save
from SQL client directly to your project resources directory as you work
I was proposing having both properties be maxes, not mins; whichever we hit
first is the limit. I agree that not having a cap on the total number of
tests performed is dangerous (I wouldn't really set it to max int; just
something pretty high). However, there is some precedent for unbounded
tests:
On 9/3/14 8:53 AM, Michael Berman wrote:
> Thanks for the feedback Phil!
>
>
>> One way to do this would be to have the current property be a cap on
>> the total number of tests performed, but the new one basically
>> control the number done per key. So if, e.g. numTestsPerEvictionRun
>> is 12, nu
Github user salyh closed the pull request at:
https://github.com/apache/commons-codec/pull/2
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
