Turns out it conflicts with the other Hibernate general meeting on IRC.
So we are moving it up 30 mins from 16:00 to 17:00 CET.
> On 3 févr. 2014, at 20:58, Emmanuel Bernard wrote:
>
> This is Tuesday 4 (tomorrow) from 16:30 to 17:30 CET. Everyone's invited :)
>
> Ps: I thought I was to blame
I see I'm now having a dependency pulled in by maven to:
org.jboss.logging:jboss-logging-annotations
This is being included as a transitive dependency via each of:
- org.hibernate:hibernate-core:jar:4.3.1.Final
- org.hibernate:hibernate-testing:jar:4.3.1.Final
- org.hibernate:hibernate-ent
> On 3 févr. 2014, at 21:57, Martin Braun wrote:
> > I have to admit, I am a bit skeptical on a few things:
> > - having to extend a technical class
> I am too, As stated in the e-mail before I want to get away from that design
> but I still
> want to be able to write queries myself if I want t
The example API I was thinking about is
http://docs.jboss.org/hibernate/orm/4.3/manual/en-US/html_single/#querycriteria-examples
> On 3 févr. 2014, at 21:57, Martin Braun wrote:
>
> HI Emmanuel,
> Hi Martin,
>
> > That's interesting. I have a couple of questions for you.
> > What is the notion
> On 3 févr. 2014, at 15:21, Sanne Grinovero wrote:
>
>> On 3 February 2014 13:33, Emmanuel Bernard wrote:
>> Hum, with the fact that this object now points to metadata, I wonder if
>> we should force EhCache, Map and Infinispan to have their own version of
>> EntityKey / RowKey and Associatio
HI Emmanuel,
Hi Martin,
> That's interesting. I have a couple of questions for you.
> What is the notion of profile and when would you use it?
This can be used when you'd like to be able to use the same queryBean in
different contexts
sou you don't have to write a different Bean if you only need
Hi Martin,
That's interesting. I have a couple of questions for you.
What is the notion of profile and when would you use it?
When do you need and use sub query ids?
The issue you had was to map getters to query parameters in an easier way than
currently possible, correct? It reminds me a litt
Hi again,
hardy is right. Here is a longer version of the proposal (that is more
discussion friendly):
> I had a quick look at the code, but for the sake of discussion, it would be
> great if you could outline
> your approach in an email. Maybe with some example code? It would make it
> mu
Hi Martin,
great that you like Hibernate Search and want to make it even easier to use.
On 3 Jan 2014, at 19:08, Martin Braun wrote:
> I am currently working on a new way to query in Hibernate Search. It's not
> finished, but
> it already works.
I had a quick look at the code, but for the sak
This is Tuesday 4 (tomorrow) from 16:30 to 17:30 CET. Everyone's invited :)
Ps: I thought I was to blame for freenode issues but apparently no :)
> On 3 févr. 2014, at 20:01, Sanne Grinovero wrote:
>
> If IRC doesn't work at the selected time, let's use:
> https://gitter.im/hibernate/hibernate-
If IRC doesn't work at the selected time, let's use:
https://gitter.im/hibernate/hibernate-search
On 3 February 2014 15:17, Emmanuel Bernard wrote:
> Resending as I screwed up the Hibernate Dev email.
>
> On Mon 2014-02-03 14:28, Emmanuel Bernard wrote:
>> Hello Hardy, Sanne and all,
>>
>> I thin
Oops, to everyone this time :)
Hibernate automatically determines the Dialect to use based on JDBC
metadata *if* a Dialect is not explicitly set. In fact letting it auto
detect is the recommended behavior, just setting Dialect explicitly when
using a custom Dialect for some reason. There is also
Hi,
I am currently working on a new way to query in Hibernate Search. It's not
finished, but
it already works. I am planning on extending the functionality a lot in the
future and
I thought this could be a nice addition to Hibernate Search. What do you think?
https://github.com/s4ke/Hibernat
Hey,
My Hibernate knowledge is really dated, but, within a Wildfly/AS7/JPA
deployment don't you still have to specify the SQL dialect in your
persistence.xml? Or is this automatically figured out now?
I have a user that is seeing postgres org.postgresql.util.PSQLException:
ERROR: operator doe
Resending as I screwed up the Hibernate Dev email.
On Mon 2014-02-03 14:28, Emmanuel Bernard wrote:
> Hello Hardy, Sanne and all,
>
> I think it's time to discuss the schedule we want for Hibernate Search
> 5. While we don't usually use time boxing, it's still useful to try and
> shoot for a roug
On Mon 2014-02-03 14:58, Sanne Grinovero wrote:
> On 3 February 2014 13:34, Emmanuel Bernard wrote:
> > On Sat 2014-02-01 18:47, Sanne Grinovero wrote:
> >> On 27 January 2014 10:32, Gunnar Morling wrote:
> >> > Looking at the issues which have been addressed or are work in progress
> >> > since
On 3 February 2014 13:34, Emmanuel Bernard wrote:
> On Sat 2014-02-01 18:47, Sanne Grinovero wrote:
>> On 27 January 2014 10:32, Gunnar Morling wrote:
>> > Looking at the issues which have been addressed or are work in progress
>> > since the last release [1] I don't think we need a tag.
>>
>> +1
2014/2/3 Sanne Grinovero
> On 3 February 2014 13:33, Emmanuel Bernard wrote:
> > Hum, with the fact that this object now points to metadata, I wonder if
> > we should force EhCache, Map and Infinispan to have their own version of
> > EntityKey / RowKey and AssociationKey (or an appropriate exter
2014/2/3 Sanne Grinovero
> On 3 February 2014 12:12, Gunnar Morling wrote:
> > 2014/2/3 Sanne Grinovero
> >>
> >> If you store anything in Infinispan, it should at the very least be
> >> Serializable.
> >>
> >> A better solution would be to provide custom Externalizers:
> >> https://hibernate.a
On 3 February 2014 13:33, Emmanuel Bernard wrote:
> Hum, with the fact that this object now points to metadata, I wonder if
> we should force EhCache, Map and Infinispan to have their own version of
> EntityKey / RowKey and AssociationKey (or an appropriate externalizer).
Ok to consider it, but l
On 3 February 2014 12:12, Gunnar Morling wrote:
> 2014/2/3 Sanne Grinovero
>>
>> If you store anything in Infinispan, it should at the very least be
>> Serializable.
>>
>> A better solution would be to provide custom Externalizers:
>> https://hibernate.atlassian.net/browse/OGM-37
>
>
> Ah, I see.
On Sat 2014-02-01 18:47, Sanne Grinovero wrote:
> On 27 January 2014 10:32, Gunnar Morling wrote:
> > Looking at the issues which have been addressed or are work in progress
> > since the last release [1] I don't think we need a tag.
>
> +1 especially as I understand JPA 2.1 is backwards compatib
Hum, with the fact that this object now points to metadata, I wonder if
we should force EhCache, Map and Infinispan to have their own version of
EntityKey / RowKey and AssociationKey (or an appropriate externalizer).
Emmanuel
On Mon 2014-02-03 11:56, Gunnar Morling wrote:
> Hi,
>
> I'm wondering
2014/1/21 Sanne Grinovero
> On 21 January 2014 13:25, Gunnar Morling wrote:
> > 2014/1/21 Sanne Grinovero
> >>
> >> I don't know if that's explicitly defined in the spec, but even if it
> >> wasn't I wouldn't be happy as a user to see an exception for such a
> commonly
> >> used feature.
> >
>
2014/2/3 Sanne Grinovero
> If you store anything in Infinispan, it should at the very least be
> Serializable.
>
> A better solution would be to provide custom Externalizers:
> https://hibernate.atlassian.net/browse/OGM-37
Ah, I see. I like the Externalizer approach as I found it surprising tha
If you store anything in Infinispan, it should at the very least be
Serializable.
A better solution would be to provide custom Externalizers:
https://hibernate.atlassian.net/browse/OGM-37
On 3 February 2014 10:56, Gunnar Morling wrote:
> Hi,
>
> I'm wondering why org.hibernate.ogm.grid.Associati
Hi,
I'm wondering why org.hibernate.ogm.grid.AssociationKey implements
Serializable. When is it actually serialized?
I'm suspecting the answer is "never", as the type of the "metadata" member
is not serializable, so I'd expect a NotSerializableException to be raised.
If so, does anything speak a
27 matches
Mail list logo
