It's back up.
On 14 déc. 2012, at 19:34, Gunnar Morling wrote:
> Hi,
>
> Emmanuel said he wanted to contact Max, not sure what came out of this.
>
> --Gunnar
> Am 14.12.2012 18:56 schrieb "Steve Ebersole" :
>
>> Nope, but I'll look into it.
>>
>> On Fri 14 Dec 2012 10:53:27 AM CST, Gunnar M
My initial reaction is if you really need transactional consistency is to do
run a transaction commit every n operations. But that may not be ok for your
application.
We could imagine more or less what you are describing. This is an idea we want
to explore to offer consistency between the index
Hi all,
Recently Steve and I spoke on IRC about compiling code on JDK 7 but
targeting Java 6 for the built artifacts.
While setting source and target level to 1.6 makes sure that the source and
byte code are compliant with Java 6, there is still the possibility of
inadvertently using classes/meth
There are at least 2 different approaches:
#1
What Emmanuel describes is to write in a structure which allows for
queries as well, so to be able to include uncommitted changes in
queries.
It should be possible to pick such a structure in a way which could
- make use of temporary storage out of me
Hi Emmanuel, Sanne,
On Mon, Dec 17, 2012 at 12:25 PM, Sanne Grinovero wrote:
> 2#
> I didn't see Guillaume asking about queries, so assuming he would just
> need a large write buffer where to keep the current Documents; this is
> a simpler patch as we already do build such a plan during any index
Hi,
I used Hibernate 2 in my software and now I'm using Hibernate 4.
Before the version migration, the method Query.setParameter(p, 1) -
[Integer values in boolean properties] - works well for setting
boolean properties.
Now, in Hibernate 4, doesn't work anymore.
Anyone could help me?
_
Just to make sure I understand...
You have a domain attribute that is boolean, but you want to treat it as
a number?
I.e.:
@Entity class Listing {
...
boolean active;
}
Query q = session.createQuery( "from Listing l where listing.active =
:isActive" );
q.setParameter( "isActive", 1 );
Correct.
In Hibernate 2, this example with 'q.setParameter( "isActive", 1 );' works !
In Hibernate 4 doesn't work.
Is there any way to make work in Hibernate 4 without modify the
implementation of my method?
(i.e. I want to use 'q.setParameter( "isActive", 1 );' )
Observation: In the database
No, that is no longer possible. You have a boolean, you should set a
boolean.
On 12/17/2012 09:12 AM, Oto Júnior wrote:
> Correct.
>
> In Hibernate 2, this example with 'q.setParameter( "isActive", 1 );' works !
> In Hibernate 4 doesn't work.
>
> Is there any way to make work in Hibernate 4 wit
I will create a jira for this regression (2lc invalidation not being
sent in a cluster) targeting Hibernate ORM 4.1.10.
Currently, I'm getting a jira error "Version with id '4.1.9' does not
exist" when attempting to create the jira.
On 12/14/2012 10:38 PM, Scott Marlow wrote:
>
> From the TR
On 12/17/2012 10:35 AM, Scott Marlow wrote:
> I will create a jira for this regression (2lc invalidation not being
> sent in a cluster) targeting Hibernate ORM 4.1.10.
>
> Currently, I'm getting a jira error "Version with id '4.1.9' does not
> exist" when attempting to create the jira.
HHH-7871 is
Yes Eric, this is a project/implementation detail.
I wrote here just for a "extra-information" of my problem. But you're right.
Thanks.
___
Oto Soares Coelho Júnior
otojun...@gmail.com / ot...@dcc.ufmg.br
Departamento de Ciência da Computação -
12 matches
Mail list logo
