11:16 a.m.
Let's keep this on list ok? Thanks.
First, have you seen the new hibernate-java8 module that is part of 5.0?
Some replies in-line...
But I am curious what would be your opinion on this extended API idea
and
approach that I took and whether you would for instance consider taking it
under the hibernate umbrella as a kind of official extension in future.
Hard to say. More than likely the next major release will drop support for
Java 6. I personally see no benefit in supporting "just" 7, so I'd likely
go right to 8.
At the moment I would like to focus on three things:
- Introduce typed (generic) queries, because at this moment streams of
Object's
are not quite useful.
Yes, we should certainly do this. I just made some Session methods
generic, so this certainly fits. But this is not Java 8 specific in any
way...
- Enable registration of LocaleDate, LocalTime as query params.
You can do that now:
* org.hibernate.Query#setParameter(java.lang.String, java.lang.Object)
* org.hibernate.Query#setParameter(java.lang.String, java.lang.Object,
org.hibernate.type.Type)
I assume you mean adding method signatures accepting those specific types?
- Custom type handlers for LocalDate, LocalTime
- Custom type handlers for Optional<?>
No idea what you mean here. What do you mean by "type handler"?
And as far as using LocalDate, etc as query parameters... you can do that
now. Do you mean specific methods accepting them?
If you could help me with one thing on the regarding the Optional
attributes
mapping. As my understanding is correct the relation/entity
mapping are being handled by OneToOneType, ManyToOneType classes. To your
knowledge would it be possible to provide an overrided version of them, or
it would rather require to alter them directly in Hibernate core?
As I understand it (I have not looked overly deeply yet), we would
essentially need a Type representing Optional that wraps an "underlying
Type". It is very similar to the idea of AttributeConverters. We could
handle it at a lower lecvel here too like we do for AttributeConverter.
12:51 p.m.
New subject: Hibernate O/RM Java 8 API.
2015-05-19 18:16 GMT+02:00 Steve Ebersole <steve(a)hibernate.org>:
Let's keep this on list ok? Thanks.
First, have you seen the new hibernate-java8 module that is part of 5.0?
Ahh, I somehow miss that, going to take a look right away.
>
> At the moment I would like to focus on three things:
> - Introduce typed (generic) queries, because at this moment streams of
Object's are not quite useful.
Yes, we should certainly do this. I just made some Session methods
generic, so this certainly fits. But this is not Java 8 specific in any
way...
> - Enable registration of LocaleDate, LocalTime as query params.
You can do that now:
* org.hibernate.Query#setParameter(java.lang.String, java.lang.Object)
* org.hibernate.Query#setParameter(java.lang.String, java.lang.Object,
org.hibernate.type.Type)
I assume you mean adding method signatures accepting those specific types?
Yes, I meant a convinient methods similar to those setDate and setTime,
something like setLocalDate, setLocalTime
>
> - Custom type handlers for LocalDate, LocalTime
>
> - Custom type handlers for Optional<?>
Sorry for ambiguity. I was refering to "custom user types" from the
reference, this is at least my understanding how Hibernate maps the Object
to SQL in general.
To sum up what I would like to be able to do "mapping" of an entity as
fallows:
class Employee {
Optional<Employee> manager;
LocalDate createDate;
LocalDate updateDate;
}
So some extra org.hibernate.type.Type definitions will be needed similar to
those that you had defined in hibernate-java8.
>
> If you could help me with one thing on the regarding the Optional
attributes mapping. As my understanding is correct the relation/entity
mapping are being handled by OneToOneType, ManyToOneType classes. To your
knowledge would it be possible to provide an overrided version of them, or
it would rather require to alter them directly in Hibernate core?
As I understand it (I have not looked overly deeply yet), we would
essentially need a Type representing Optional that wraps an "underlying
Type". It is very similar to the idea of AttributeConverters. We could
handle it at a lower lecvel here too like we do for AttributeConverter.
Cool, I will explore this a bit more and see what I could do with that.
Thanks,
Jakub
3:52 p.m.
New subject: Hibernate O/RM Java 8 API.
On Tue, May 19, 2015 at 12:51 PM, Jakub Narloch <jmnarloch(a)gmail.com> wrote:
2015-05-19 18:16 GMT+02:00 Steve Ebersole <steve(a)hibernate.org>:
>
> > - Enable registration of LocaleDate, LocalTime as query params.
>
> You can do that now:
> * org.hibernate.Query#setParameter(java.lang.String, java.lang.Object)
> * org.hibernate.Query#setParameter(java.lang.String, java.lang.Object,
> org.hibernate.type.Type)
>
> I assume you mean adding method signatures accepting those specific types?
>
Yes, I meant a convinient methods similar to those setDate and setTime,
something like setLocalDate, setLocalTime
But that would in fact introduce a Java 8 dependency on hibernate-core if
we did this directly. We could maybe use some form of "unwrap" notion
where hibernate-java8 could auto-register some delegate for "additional
param setting". We could use the same concept in relation to
hibernate-spatial as well for setting geolatte specific parameters.
> >
> > - Custom type handlers for LocalDate, LocalTime
> >
> > - Custom type handlers for Optional<?>
>
Sorry for ambiguity. I was refering to "custom user types" from the
reference, this is at least my understanding how Hibernate maps the Object
to SQL in general.
To sum up what I would like to be able to do "mapping" of an entity as
fallows:
class Employee {
Optional<Employee> manager;
LocalDate createDate;
LocalDate updateDate;
}
As far as the Java 8 date/time stuff... see the hibernate-java8 module...
that is its whole goal... Optional support has a little more to it, some
of which is alluded to in this discussion
So some extra org.hibernate.type.Type definitions will be needed similar
to those that you had defined in hibernate-java8.
Um, why would we need extra*s*? We need one... for Optional.
10:37 a.m.
New subject: Hibernate O/RM Java 8 API.
Hi Steve,
Sorry for disapearing for a bit, but I would like to get back to this
thread.
I guess there might be some miscommunication from my side about what I
would like to introduce into my extension and what I would like to
contribute to Hibernate ORM directly.
So to sum up I've continued working on my little project:
https://github.com/jmnarloch/hstreams - and made the first public release.
So if anyone wish to use Hibernate with Java 8 he is free to go.
I've basically added everything that we had talk about: that is Optional
query results, operating on Streams of query results, typed queries.
I had noticed that Hibernate 5 will additionally add support for JDK 8
dates API, so I'm planning to reuse that.
What more the extension can be already used with Hibernate 4.3.x and unless
you decide to move to Java 8 I can release another version that will be
compatible with Hibernate 5 .
Now I'm aware that this would be short living sub project till the moment
the Hibernate will migrate to Java 8, but untill that I can work on it.
Also If you decide to migrate finally to latest Java version, I would be
happy to prepare some pull requests based on the ideas I had already
implemented in this side project.
Regards,
Jakub Narlohc
2015-05-19 22:52 GMT+02:00 Steve Ebersole <steve(a)hibernate.org>:
On Tue, May 19, 2015 at 12:51 PM, Jakub Narloch
<jmnarloch(a)gmail.com>
wrote:
>
>
> 2015-05-19 18:16 GMT+02:00 Steve Ebersole <steve(a)hibernate.org>:
>>
>> > - Enable registration of LocaleDate, LocalTime as query params.
>>
>> You can do that now:
>> * org.hibernate.Query#setParameter(java.lang.String, java.lang.Object)
>> * org.hibernate.Query#setParameter(java.lang.String, java.lang.Object,
>> org.hibernate.type.Type)
>>
>> I assume you mean adding method signatures accepting those specific
>> types?
>>
> Yes, I meant a convinient methods similar to those setDate and setTime,
> something like setLocalDate, setLocalTime
>
But that would in fact introduce a Java 8 dependency on hibernate-core if
we did this directly. We could maybe use some form of "unwrap" notion
where hibernate-java8 could auto-register some delegate for "additional
param setting". We could use the same concept in relation to
hibernate-spatial as well for setting geolatte specific parameters.
>
>> >
>> > - Custom type handlers for LocalDate, LocalTime
>> >
>> > - Custom type handlers for Optional<?>
>>
> Sorry for ambiguity. I was refering to "custom user types" from the
> reference, this is at least my understanding how Hibernate maps the Object
> to SQL in general.
> To sum up what I would like to be able to do "mapping" of an entity as
> fallows:
>
> class Employee {
>
> Optional<Employee> manager;
>
> LocalDate createDate;
> LocalDate updateDate;
> }
>
As far as the Java 8 date/time stuff... see the hibernate-java8 module...
that is its whole goal... Optional support has a little more to it, some
of which is alluded to in this discussion
>
> So some extra org.hibernate.type.Type definitions will be needed similar
> to those that you had defined in hibernate-java8.
>
Um, why would we need extra*s*? We need one... for Optional.
3457
days inactive
3486
days old
3 comments
2 participants
participants (2)
-
Jakub Narloch -
Steve Ebersole