anonymously or if it ask to create an account. It says:
"We don't recognize that email address"
>
> On Thu, Oct 26, 2017 at 1:25 PM Robert Marcano <mailto:rob...@marcanoonline.com>> wrote:
>
> On 10/26/2017 12:03 PM, Steve Ebersole wro
s to join. Not because anonymity was
important, just tired of creating accounts for a few days usage in
another service. Just my 2 cents.
There are other advantages but are more "political" than practical (OSS,
federated, etc).
>
> On Thu, Oct 26, 2017 at 10:52 AM Robert Marcano
>
On 10/26/2017 09:22 AM, Sanne Grinovero wrote:
> Thanks, I had the same on my TODO list. Are you going to convert the
> HipChat team?
Just out of curiosity from someone that has just 2 weeks subscribed to
this mailing list. Why not try Riot/Matrix http://riot.im/ ?
>
> That way we *could* all t
On 10/16/2017 10:13 AM, Steve Ebersole wrote:
> On Mon, Oct 16, 2017 at 9:00 AM Robert Marcano <mailto:rob...@marcanoonline.com>> wrote:
>
> No, I know implicitly closing the JDBC statement is not possible with
> only the current CallableStatement API. There is
On 10/11/2017 03:15 PM, Vlad Mihalcea wrote:
> You can open a GitHub issue for JPA. Meanwhile, you can work around it
> as you suggested.
Opened an issue on JPA spec https://github.com/javaee/jpa-spec/issues/162
>
> On 11 Oct 2017 9:08 pm, "Robert Marcano" <mailto
rocedureQuery
implementing some kind of prepareCall() method that return a stateful
object that implement AutoCloseable.
>
> So what is that condition? That's the rub...
>
>
> On Wed, Oct 11, 2017 at 1:07 PM Robert Marcano <mailto:rob...@marcanoonline.com>>
Migrating code from the Hibernate API to JPA, I found a stored procedure
being called on a loop that was generating DB2 errors [1] on tests. This
error is caused in this case for having a lot of not closed statements.
The problem didn't happen using ProcedureCall Hibernate API because the
metho
