Any concrete reason why we cannot add comments, cache mode and read only
to the named query definitions (except that no one had time so far)?
There are only runtime params right now and I don't see any counter
argument.
I'll add them if no one complains.
---
Go ahead.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Emmanuel Bernard
Sent: Thursday, 18 August 2005 9:01 AM
To: hibernate-devel@lists.sourceforge.net
Subject: [Hibernate] Extra info at definition time
Any concrete reason why we cannot add comments,
Artifacts (ie hbm files and annotated classes) were not able to point
to the same entity-name (== class name for annotations) in an
AnnotationConfiguration object: a duplicate mapping exception were
raised.
I've added an hibernate.artifact property (we need to find a
good name), to allow prece
But the
drawback is that I need to delay all the binding operation till the
actual buildSessionFactory() launch, and thus keeping a list of classes
and Document to be processed. This consumes more memory (higher peak
until the buildSessionFactory call), but its probably not a show stopper.
That
I don't understand what is the problem you are trying to
solve?
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Emmanuel BernardSent: Thursday, 18 August 2005 8:54
PMTo: hibernate-devel@lists.sourceforge.netSubject:
[Hibernate] Configuration artifact precedence
Artifacts (
When the users has both hbm.xml and annotations in his project (most
likely doing their migration phase).
I don't get why it needs special attention (besides just take what comes
first), but if there is
a reason for it then it sounds like hibernate.mappingprecedence would be a
better name
