I feel uncomfortable to make it in Hibernate since the hibernate
configuration is not screwed up (at least not in this area). opening
this door would lead to properties vs programmatic API inconsistency
priorities and/or user unexpectation.
Max Rydahl Andersen wrote:
On Tue, 22 Nov 2005 20:52
On Tue, 22 Nov 2005 20:52:30 +0100, Emmanuel Bernard
<[EMAIL PROTECTED]> wrote:
In HEM I have to since the configuration process is standardised, The
only way to provide this feature is through configuration.
Yes I know it is required for HEM and just wondering why we dont also
just add it
In HEM I have to since the configuration process is standardised, The
only way to provide this feature is through configuration.
Max Rydahl Andersen wrote:
I fail to understand why its ok to add naming_strategy to ejb3
configuration and not hibernate configuration?
/max
--- Forwa
Hi,
There is a serious bug still present in 3.1rc2 (and I guess
in rc3 since it is still open):
http://opensource2.atlassian.com/projects/hibernate/browse/HHH-957
It is a ClassCastException when using DetachedQueries, what
is really needed and useful when perfoming subqueries. I
Hi,
I agree with you concerning the need for this feature. All my latest
development was based on the criteria API, since it seemed quite complete at
the moment I decided to use it. And it actually made its code much simpler,
until I had to change my infra-structure when I realized that outer join
