[Hibernate] Hibernate Tools 3.0 alpha 4
The new updated version of the Hibernate Tools project includes significant updates to the Eclipse editors, plugings, and wizards, as well as a unified and convenient Ant task for integration of the tools in your regular builds. See the What's New overview or download directly. http://www.hibernate.org/hib_docs/tools/newandnoteworthy/hibernate- eclipse-news-3.0.0.alpha4.html http://sourceforge.net/project/showfiles.php? group_id=40712&package_id=141977 --- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
Re: [Hibernate] Scope of Hibernate 3.1
As you all know, I am still just not sold on this.
Can you try and explain why not ? ;)
Keeping adding syntatic sugar to hql (like new list, new map) sounds
to rigid when it could be done pretty nicely with something like
the result transformer...and it allow users to do whatever they want
with the different items.
-max
-Original Message-
From: Max Andersen
Sent: Wednesday, 8 June 2005 3:15 PM
To: Gavin King; hibernate-devel@lists.sourceforge.net
Subject: Re: [Hibernate] Scope of Hibernate 3.1
Adding the ResultTransformer or similar to native sql and hql
(http://opensource.atlassian.com/projects/hibernate/browse/HHH-587)
Would complete the query result and entitymode possibilites.
-max
I've put some thought into the scope of work for Hibernate 3.1.
Here's what I came up with:
* Finish bulk update/delete, including, HHH-352
* Clean up tuple package and make it truly extensible
* Auto-detect {..} in queries, HHH-596
* Support {coll.key}, etc, TODO-109
* Support in , HHH-381
* Support XML based named result set mappings, HHH-597
* Support joins in DetachedCriterias when used for subselecting
* Keep readonly entities in soft references TODO-162
* Maybe attribute-level query space granularity
* Maybe add bulk insert ... select
* Maybe finish StatelessSession stuff for customer
* Maybe transform(), HHH-175
So there are three main broad areas here:
* native SQL enhancements
* bulk HQL functionality
* performance tuning for "large" sessions
Along with a couple of other small things.
Thoughts?
---
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
___
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Scope of Hibernate 3.1
As you all know, I am still just not sold on this.
-Original Message-
From: Max Andersen
Sent: Wednesday, 8 June 2005 3:15 PM
To: Gavin King; hibernate-devel@lists.sourceforge.net
Subject: Re: [Hibernate] Scope of Hibernate 3.1
Adding the ResultTransformer or similar to native sql and hql
(http://opensource.atlassian.com/projects/hibernate/browse/HHH-587)
Would complete the query result and entitymode possibilites.
-max
> I've put some thought into the scope of work for Hibernate 3.1.
>
> Here's what I came up with:
>
>
> * Finish bulk update/delete, including, HHH-352
> * Clean up tuple package and make it truly extensible
> * Auto-detect {..} in queries, HHH-596
> * Support {coll.key}, etc, TODO-109
> * Support in , HHH-381
> * Support XML based named result set mappings, HHH-597
> * Support joins in DetachedCriterias when used for subselecting
> * Keep readonly entities in soft references TODO-162
>
>
> * Maybe attribute-level query space granularity
> * Maybe add bulk insert ... select
> * Maybe finish StatelessSession stuff for customer
> * Maybe transform(), HHH-175
>
>
> So there are three main broad areas here:
>
>
> * native SQL enhancements
> * bulk HQL functionality
> * performance tuning for "large" sessions
>
>
> Along with a couple of other small things.
>
>
> Thoughts?
>
---
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r
___
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
Re: [Hibernate] Scope of Hibernate 3.1
Adding the ResultTransformer or similar to native sql and hql
(http://opensource.atlassian.com/projects/hibernate/browse/HHH-587)
Would complete the query result and entitymode possibilites.
-max
I've put some thought into the scope of work for Hibernate 3.1.
Here's what I came up with:
* Finish bulk update/delete, including, HHH-352
* Clean up tuple package and make it truly extensible
* Auto-detect {..} in queries, HHH-596
* Support {coll.key}, etc, TODO-109
* Support in , HHH-381
* Support XML based named result set mappings, HHH-597
* Support joins in DetachedCriterias when used for subselecting
* Keep readonly entities in soft references TODO-162
* Maybe attribute-level query space granularity
* Maybe add bulk insert ... select
* Maybe finish StatelessSession stuff for customer
* Maybe transform(), HHH-175
So there are three main broad areas here:
* native SQL enhancements
* bulk HQL functionality
* performance tuning for "large" sessions
Along with a couple of other small things.
Thoughts?
---
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
___
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Enhanced filtering?
I am against changing the concept here. I think the original conception is the only one that truly makes sense. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Ebersole Sent: Wednesday, 8 June 2005 10:36 AM To: Emmanuel Bernard; hibernate-devel@lists.sourceforge.net Subject: RE: [Hibernate] Enhanced filtering? We were just talking about the delete use case last night in relation to bulk deletes. I think it really comes down to how we want to conceptualize the filters. Initially they were envisioned solely as a mechanism for filtering returned data. What we are talking about here is a serious expansion on that original conceptualization with serious ramifications in terms of caching. The one that is really difficult is the get/load scenario, as that then supposes extension out to to-one associations. Not sure how a filter (where condition) would even play into an insert... Even with deletes though, I can see what you are saying if the filters are security-based, but what if the filters are temporal. Do we really want to limit the deleted rows there? At any rate, I'd prefer instead that this kind of stuff were handled through the events like the JACC stuff does. -1 My $.02 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Emmanuel Bernard Sent: Wednesday, June 08, 2005 7:26 AM To: hibernate-devel@lists.sourceforge.net Subject: [Hibernate] Enhanced filtering? I get some feedbacks from users using filters. Some of them seems to be *keen on* enhancing the filter capability to all session operations - load/get - save/update - delete It makes sense for permissioned data as a global filtering. The thing is that it needs to lower Hibernate capability (workaround update counts breaking etc, versioning issue). What do you guys think of that? --- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel --- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel --- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] Scope of Hibernate 3.1
I’ve put some thought into the scope of work for
Hibernate 3.1.
Here’s what I came up with:
Finish bulk update/delete, including,
HHH-352
Clean up tuple package and make
it truly extensible
Auto-detect {..} in queries,
HHH-596
Support {coll.key}, etc,
TODO-109
Support
in , HHH-381
Support XML based named result
set mappings, HHH-597
Support joins in
DetachedCriterias when used for subselecting
Keep readonly entities in soft
references TODO-162
Maybe attribute-level query
space granularity
Maybe add bulk insert …
select
Maybe finish StatelessSession
stuff for customer
Maybe transform(), HHH-175
So there are three main broad areas here:
native SQL enhancements
bulk HQL functionality
performance tuning for “large”
sessions
Along with a couple of other small things.
Thoughts?
RE: [Hibernate] Enhanced filtering?
We were just talking about the delete use case last night in relation to bulk deletes. I think it really comes down to how we want to conceptualize the filters. Initially they were envisioned solely as a mechanism for filtering returned data. What we are talking about here is a serious expansion on that original conceptualization with serious ramifications in terms of caching. The one that is really difficult is the get/load scenario, as that then supposes extension out to to-one associations. Not sure how a filter (where condition) would even play into an insert... Even with deletes though, I can see what you are saying if the filters are security-based, but what if the filters are temporal. Do we really want to limit the deleted rows there? At any rate, I'd prefer instead that this kind of stuff were handled through the events like the JACC stuff does. -1 My $.02 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Emmanuel Bernard Sent: Wednesday, June 08, 2005 7:26 AM To: hibernate-devel@lists.sourceforge.net Subject: [Hibernate] Enhanced filtering? I get some feedbacks from users using filters. Some of them seems to be *keen on* enhancing the filter capability to all session operations - load/get - save/update - delete It makes sense for permissioned data as a global filtering. The thing is that it needs to lower Hibernate capability (workaround update counts breaking etc, versioning issue). What do you guys think of that? --- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel --- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] Enhanced filtering?
I get some feedbacks from users using filters. Some of them seems to be *keen on* enhancing the filter capability to all session operations - load/get - save/update - delete It makes sense for permissioned data as a global filtering. The thing is that it needs to lower Hibernate capability (workaround update counts breaking etc, versioning issue). What do you guys think of that? --- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
