Migration of the Hibernate email lists to their new hosting home is now
complete. As of today, automated emails have been fully cut over:
JIRA - [EMAIL PROTECTED]
SVN - [EMAIL PROTECTED]
CruiseControl - hibernate-dev@lists.jboss.org
For the past 2 weeks or so I have been monitoring both of the
Not sure if anyone replied to this yet or not, so I'll throw my $0.02
into the discussion. I think all that is needed is to better allow
definition of what is to occur during replication in the method call.
For example, consider the changing the signature from accepting a
ReplicationMode to
So Scott has finished up HHH-1931 in regards to the cglib
instrumentation task.
The underlying issue was that the javassist and cglib versions did
slightly different things in regards to instrumenting field access.
Javassist only instrumented access to fields which are declared on the
class
I am working on enhancing Derby support a little bit, but have run into
an issue with their syntax that I am unable to figure out. I was hoping
someone on this list was familiar enough with Derby to point me in the
right direction.
Specifically, I am trying to properly deal with the manner in
Andersen
Sent: Tuesday, July 25, 2006 12:35 PM
To: Steve Ebersole
Cc: Hibernate development
Subject: Re: [Hibernate] Roadmap - components
Regarding handling users migration of code then I guess (one of) the
worst
parts is where users have query/criteria building code that does not
have
direct access
Regarding the HQL translator related changes mentioned in the previous
email...
Mainly, this is involving a fairly large scale refactoring of the Antlr
grammars and the associated code.
The first aspect was previously discussed on this list, so I won't go
into all the gory details. Basically,
Yep. This has already been fixed for almost two months now in SVN ;)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Thursday, July 20, 2006 8:35 AM
To: hibernate-devel@lists.sourceforge.net
Cc: [EMAIL PROTECTED]
Subject:
FYI...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Wednesday, July 19, 2006 9:12 AM
To: [EMAIL PROTECTED]
Subject: [Hibernate-commits] Hibernate Code SVN: r10125 -
branches/Branch_3_2
Author: [EMAIL PROTECTED]
Date: 2006-07-19
Now that 3.2.0.ga is imminent, here are the things which are currently
underway, or which I would like to start soon:
1) Antlr query translator redesign. The original Antlr-based translator
was a great first cut and showed us the usefulness of Antlr for this
task; in many ways it ways a learning
Type is *NOT* a public API...
-Original Message-
From: Max Andersen
Sent: Monday, July 17, 2006 10:38 AM
To: Steve Ebersole; Hibernate development
Subject: Re: [Hibernate] Roadmap - components
...but requires changes to public API so probably best suited for 3.3.
Regarding
in the underlying Type system...
-Original Message-
From: Max Andersen
Sent: Monday, July 17, 2006 10:43 AM
To: Steve Ebersole; Hibernate development
Subject: Re: [Hibernate] Roadmap - components
On Mon, 17 Jul 2006 17:41:25 +0200, Steve Ebersole
[EMAIL PROTECTED] wrote:
Type
: Monday, July 17, 2006 9:50 AM
To: Steve Ebersole; Hibernate development
Subject: Re: [Hibernate] Roadmap
1) Antlr query translator redesign. The original Antlr-based
translator
was a great first cut and showed us the usefulness of Antlr for this
task; in many ways it ways a learning experience
Hibernate version 3.2.0.cr3 has just been released. The download and
notes are available from
http://sourceforge.net/project/showfiles.php?group_id=40712package_id=1
27784release_id=430157
This is mainly a minor bug-fix release, although there are further
enhancements and fixes for JPA
I'll look at other issues after JPA work is complete. The hope is to
release the final 3.2.0 CR after that work is complete. So I would
expect anything else to be bundled into 3.2 point releases. The DTD
thing is an obvious typo and is trivial to fix, so I'll correct that.
-Original
...
-Original Message-
From: Emmanuel Bernard [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 21, 2006 4:59 PM
To: Steve Ebersole
Cc: Hibernate development
Subject: Re: [Hibernate] New error on Annotation query
My description was too generic. I've updated the GeneralTest by adding
Actually, I just tested with HSQLDB. For me, HSQLDB is *also* returning
columnType = 12 for both of those scalars (and Hibernate then returns
Strings for both)...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Steve Ebersole
Sent: Thursday, June 22
Try it again from SVN.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Emmanuel Bernard
Sent: Sunday, June 18, 2006 10:21 PM
To: Hibernate development
Subject: [Hibernate] New error on Annotation query
Has something changed that I haven't propagated in
I am creating a similar test in the core testsuite and see if I can
reproduce.
-Original Message-
From: Max Andersen
Sent: Wednesday, June 21, 2006 3:53 PM
To: Emmanuel Bernard; Steve Ebersole
Cc: Hibernate development
Subject: Re: [Hibernate] New error on Annotation query
This should
] On Behalf Of
Steve Ebersole
Sent: Wednesday, June 21, 2006 3:55 PM
To: Max Andersen; Emmanuel Bernard
Cc: Hibernate development
Subject: Re: [Hibernate] New error on Annotation query
I am creating a similar test in the core testsuite and see if I can
reproduce.
-Original Message-
From: Max
From my understanding in discussions with Max, auto-discovery is illegal
once any returns have been defined/added.
Max, can you clarify here? Thinking some more about it, maybe you just
meant the column name discovery (as it should be possible to still
auto-discover types in this scenario)?
I'll take a look. That code block should only actually be executing on
dot structures, which an alias is definitely not...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Max
Rydahl Andersen
Sent: Friday, June 09, 2006 9:21 AM
To: Emmanuel Bernard
Cc:
Youre right. We should never have expected
failure type tests in a test suite so that we can get back to things we
know we want to fix. That is so crazy; what are we thinking here
And as for a projects choice of how to define
tests impacting that projects credibility in *your
projects*
Still not able to reproduce this...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Steve Ebersole
Sent: Friday, June 09, 2006 9:44 AM
To: Hibernate development
Subject: Re: [Hibernate] Query failing
I'll take a look. That code block should only
Andersen
Sent: Thursday, June 01, 2006 7:06 AM
To: Steve Ebersole; Hibernate development
Subject: Re: [Hibernate] CacheProviders
Additionally, we may want to split the Cache interface into separate
interfaces also based on usage; this would only be intended to allow
clearer definition
That sounds reasonable.
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1795
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Emmanuel Bernard
Sent: Friday, May 26, 2006 5:16 PM
To: Hibernate development
Subject: [Hibernate] Default to
I think you are looking for [EMAIL PROTECTED] But kind of hard
for them to change the persistence spec to add type to the
setParameter() methods when JPA does not even have a notion of a type.
So in your Hibernate request(s), then how do you propose that we allow
users to bind parameters of
the clear benefit
there. And I need to see a *clear* benefit before I go changing APIs
that people have been using for over two years...
-Original Message-
From: Juraj Burian [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 23, 2006 8:02 AM
To: Steve Ebersole
Cc: hibernate-devel
() and handleExplicitPropertyJoin()).
-Original Message-
From: Joshua Davis [mailto:[EMAIL PROTECTED]
Sent: Friday, May 12, 2006 3:44 PM
To: Steve Ebersole
Subject: Re: Looked at the new resolver code
Thanks for that.
RE: lhs - Okay, I was just a little confused by that when I first looked
at it... it's still
Sorry, my fault. I forgot that we
added that call to your stuff.
We really need this changed though to
properly allow for (1) classic aggregation registration and (2) better user
function registration.
The other thing I could do is add back the
old signature which would only be for
We used to implement a required feature of EJB3 that really does not
make much sense ;) It allows you to have a map/many-to-many/map
structure where the map-key comes from the target entity table (i.e.
*not* the association table).
At any rate, it probably will be added to core at some point;
Hibernate 3.2.0.CR2 has been released.
Changes mainly represent further alignments with the
latest EJB3 specifications. Two important ones to note in particular are
(1) the ability to perform bulk operations via native-sql
queries, avoiding the need to grab JDBC connections
(2)
So now that we have the BytecodeProvider abstraction, does it make sense
to allow no lazy-load capabilities for simplistic apps? Something like
a NoOpBytecodeProvider which performs no type of class enhancement?
---
This SF.Net email is
Sure at some point. But this is still a new evolving API and too
volatile for exposure...
-Original Message-
From: Emmanuel Bernard [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 23, 2006 10:13 AM
To: Steve Ebersole
Cc: Hibernate development
Subject: Re: [Hibernate] bytecode libraries
http://svnbook.red-bean.com/
-Original Message-
From: Max Andersen
Sent: Wednesday, March 22, 2006 12:23 PM
To: Emmanuel Bernard; Steve Ebersole
Cc: Hibernate development
Subject: Re: [Hibernate] branchng/tagging subversion repo
ditto ;)
You speak Chinese to me (no offense
Bernard; Steve Ebersole
Cc: Hibernate development
Subject: Re: [Hibernate] branchng/tagging subversion repo
ditto ;)
You speak Chinese to me (no offense to the language, I just don't know
it ;-) ).
Is there any good snv how to I can use as a reference before tagging
live?
Steve Ebersole
Given the current layout of the subversion repo, there is a little
quirkiness to branching and tagging of which I wanted y'all to be
aware. Namely, you need to do one of two things when doing the
svn-copy:
(1) svn-copy the *entire* project into the branch/tag; i.e. copy over
all modules
(2) do a
So we should talk about the layout of the subversion repository. We had
talked about each project getting its own module in the repository
with its own trunk/branches/tags structure.
This is easy enough for the core stuff.
But has implications for all of the current HibernateExt subprojects.
Hibernate 3.1.3 has just been released. This is mainly a bug-fix
release.
View the details at
http://sourceforge.net/project/shownotes.php?release_id=403223group_id=
40712
Download bundles are available at
http://sourceforge.net/project/showfiles.php?group_id=40712package_id=1
My new DDL generation stuff is using it. Although if I remember
correctly, I only really needed it for testing purposes. Actually
committing it was a mistake though.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Max
Rydahl Andersen
Sent: Thursday,
I've been getting them
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Max
Rydahl Andersen
Sent: Thursday, March 16, 2006 3:20 AM
To: Hibernate development
Subject: [Hibernate] commit messages?
Am I the only one not having received hibernate-commits
Or, you could just specify an index on the many-to-one/:
class name=Position ...
...
many-to-one class=Order column=order_id index=IDX_FK_POSITION_ORDER
.../
/class
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Woelke, Milan
Sent: Tuesday,
The best approach is to first just describe the changes you are
proposing at a high level here on this list (i.e. the theory).
Then we can discuss the implementation details.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Gudlaugur Egilsson
Sent:
Hibernate 3.2 alpha1 has just been released. The distribution can be
obtained at
http://sourceforge.net/project/showfiles.php?group_id=40712package_id=1
27784release_id=397557
There are some significant enhancements with this release so be sure to
check the change-log. The biggest changes
You could, and actually most of the needed code is already in place due
to the feature of scrolling collection fetches. The main problem there
is that it *only* works (in terms of what you are trying to achieve)
provided you know for certain that the results are ordered correctly
(namely, they
having a very hard time actually grabbing the backup
tarballs from SF as somehow the connections keep getting dropped on me
in the midst of the download, so I want to build in some leeway for that
as well.
-Original Message-
From: Steve Ebersole
Sent: Tuesday, February 21, 2006 10:06 AM
The EJB3-persistence-spec requires that LockModeType.READ and
LockModeType.WRITE acquire physical database update/exclusive locks for
the duration of the current transaction. Currently we have mapped
LockModeType.READ to LockMode.UPGRADE and LockModeType.WRITE to a new
LockMode.FORCE
Sure, I can get Damon to move all of it. I thought there was some stuff
you could not move due to your eclipse work?
-Original Message-
From: Max Andersen
Sent: Tuesday, February 21, 2006 11:19 AM
To: Steve Ebersole; hibernate-devel@lists.sourceforge.net
Subject: Re: [Hibernate
I kinda ignore stuff from you mostly ;)
-Original Message-
From: Max Andersen
Sent: Tuesday, February 21, 2006 3:34 PM
To: Steve Ebersole; hibernate-devel@lists.sourceforge.net
Subject: Re: [Hibernate] Subversion move
On Tue, 21 Feb 2006 18:50:38 +0100, Steve Ebersole
[EMAIL PROTECTED
The keystone of that logic is the
org.hibernate.cache.CacheConcurrencyStrategy. Have a look at the
different implementations of that interface.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of shalon
toy
Sent: Tuesday, February 14, 2006 12:30 PM
To:
Ahh [EMAIL PROTECTED]@#E
Sorry my fault. I commited the support for the new JBossCache
optimistic locking model, but forgot to commit the new jar.
Give me a sec...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Christian Bauer
Sent: Friday, February
The thing that we discussed (and I have just not yet had time to
implement) is actually converting QueryExceptions that contain antlr
stuff during serialization by either writeReplace() or writeObject().
Initially we had discussed just stripping the cause in the case of antrl
exception, but
Well I think the distinction here is that Hibernate constitutes a hard
dependency on Antlr. The users choice to use Oracle is completely
within their control.
-Original Message-
From: Max Andersen
Sent: Wednesday, February 08, 2006 8:41 AM
To: Steve Ebersole; Scott M Stark;
jboss
What does the SQL look like to access this?
-Original Message-
From: Bompart Cedric [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 08, 2006 3:40 AM
To: Steve Ebersole; hibernate-devel@lists.sourceforge.net
Subject: RE : [Hibernate] livelink collections server
Hello,
The livelink
Yes, I plan to start using these conventions starting with 3.2.
I'm not a big fan of all minor releases needing to append '.ga' (i.e.
3.1.3.ga.jar). I really wish there was a way to define ordering amongst
qualifiers.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
You should do it as part of every commit. It is far more painful to do
large occasional merges.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Max
Rydahl Andersen
Sent: Monday, February 06, 2006 4:08 AM
To: Hibernate development
Subject: [Hibernate]
BTW
I have just branched cvs for the purposes of 3.2 development, as 3.2 is
expected to introduce a number of API changes (mainly minor stuff in
some of the extension APIs) and some different behaviors required for
EJB3. The branch is named Branch_3_2 if you are interested...
advanced work on HEAD. In this case branch
for 3.1.x?
This is a very old discussion that seems to come out of my memory.
Steve Ebersole wrote:
BTW
I have just branched cvs for the purposes of 3.2 development, as 3.2
is
expected to introduce a number of API changes (mainly minor stuff in
some
@lists.sourceforge.net
Subject: Re: [Hibernate] hibernate 3.2
Steve,
is 3.1 stuff in HEAD ?
Thanks
On Thursday 02 February 2006 04:35 pm, Steve Ebersole wrote:
BTW
I have just branched cvs for the purposes of 3.2 development, as 3.2
is
expected to introduce a number of API changes (mainly minor stuff
Hibernate 3.1.2 has just been released:
http://sourceforge.net/project/showfiles.php?group_id=40712package_id=1
27784release_id=388971
This release fixes, amongst other minor bugs/enhancements, bugs with
Session closure checking, some potential bugs in HQL parameter binding,
and issues with
LOL, I am still trying to checkout that beast ;)
Thanks.
-Original Message-
From: Scott M Stark
Sent: Saturday, January 28, 2006 10:24 AM
To: Steve Ebersole; hibernate-devel@lists.sourceforge.net
Subject: RE: [Hibernate] Hibernate 3.1.2 released
This has been added
A custom Dialect should be enough, although you may need to
appropriately set some configuration properties as well...
The best thing to do is to simply try running the Hibernate test suite
using your custom dialect; that'll give you an idea of what type/level
of SQL support Hibernate is
You want the user forum: http://forum.hibernate.org/
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Srinivas Jadcharla
Sent: Friday, January 20, 2006
3:20 PM
To:
hibernate-devel@lists.sourceforge.net
Subject: [Hibernate] bind
variables Question
Hi there,
Hibernate 3.1.1 has just been released including mainly bugfixes and
minor improvements. For details check out the release notes:
http://sourceforge.net/project/shownotes.php?release_id=386304group_id=
40712
Downloads are available at:
Not all databases handle DDL the same in
terms of transactional semantics.
The simple (and most natural) solution is
to bootstrap your SessionFactory (and thus run hbm2ddl) when the app
deploys/starts-up, not on first access.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Hibernate 3.1 final has been released. It includes numerous bug-fixes
and enhancements as well as upgrades to a few libraries. For details,
check out the change log:
http://sourceforge.net/project/shownotes.php?release_id=377721group_id=
40712
The release can be downloaded at:
Already planned:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1050
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Emmanuel Bernard
Sent: Thursday, December 08, 2005 10:25 AM
To: Hibernate development
Subject: [Hibernate] HQL UNION
I
Sweet, just in time ;)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Max
Rydahl Andersen
Sent: Wednesday, December 07, 2005 2:55 PM
To: Hibernate development
Subject: [Hibernate] Fwd: antlr 2.7.6rc1 available
updated antlr rc with our fixes included
I plan on releasing 3.1 final next week, unless something unforeseen
comes up.
Please take a look at the JIRA issues assigned to you for inclusion in
3.1 to see if you will be able to complete them. Please let me know
about any issues.
Can you give me the connection info to the various db instances? I'll
try running these manually and see how long things are taking. Or have
you tried this already?
With Oracle for example, it is pretty important how the underlying
database is setup in terms of how fast/slow the testsuite runs.
6:05 AM
To: Steve Ebersole; Gavin King; Hibernate devel
Subject: RES: [Hibernate] query statistics
just a quick response.
the priorities for the tools is:
A. get the underlying sql(s)
B. get the guessed types of the parameters
C. get the locations of the parameters in HQL and SQL
A and B
query.
-Original Message-
From: Gavin King
Sent: Monday, November 21, 2005 8:55 AM
To: Steve Ebersole; 'Hibernate devel'
Subject: RE: [Hibernate] query statistics
Right. The only downside would be increased mem usage, I suppose.
-Original Message-
From: Steve Ebersole
Sent
In relation to
http://opensource2.atlassian.com/projects/hibernate/browse/HHH-73
(Statistics for HQL queries use pre-processed query string):
The original issue behind this case is now easy to fix because of the
introduction of query plans. The query plans know about the query
strings before any
I guess we could make it so. This issue is that currently it does not
know the non-expanded query.
-Original Message-
From: Gavin King
Sent: Monday, November 21, 2005 8:51 AM
To: Steve Ebersole; Hibernate devel
Subject: RE: [Hibernate] query statistics
Could the query plan cache both
Yes, futile silly inane discussions such as this one kill my enthusiasm and
interest a little bit every day...
Tell you what: you run your project the way you want, I'll not interfere;
ergo
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Leonardo
I tag CVS first, and then use that to do the build. So no problem
there...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Barry
Hawkins
Sent: Friday, November 18, 2005 6:48 PM
To: Hibernate devel
Subject: [Fwd: Re: [Hibernate] Provision of source-only
Hibernate 3.1rc3 has just been released. This release contains various
bugfixes, as well as improvements and enhancements regarding caching of
HQL and native SQL queries.
Please see the release notes and changelog for more details:
Geez... SF dev CVS is *still* down; highly annoying!
-Original Message-
From: Steve Ebersole
Sent: Friday, November 11, 2005 10:26 AM
To: Scott M Stark; Max Andersen
Cc: Hibernate development
Subject: RE: [Hibernate] you just gotta love sf.net
I plan to have a look
SQL query caching is in there...
-Original Message-
From: Max Andersen
Sent: Sunday, November 06, 2005 11:53 AM
To: Steve Ebersole; Hibernate development
Subject: Re: [Hibernate] query plans
Nice stuff - give a ping when sql query caching is in there somewhere ;)
btw. if you know
Yes, try reading what you quoted from me again ;)
-Original Message-
From: Max Andersen
Sent: Sunday, November 06, 2005 3:24 PM
To: Steve Ebersole; Hibernate development
Subject: Re: [Hibernate] query plans
SQL query caching is in there...
ok - where ? Can't find it.
And from your
As an fyi...
I just checked in a bunch of changes related to how queries
translations are cached. I added a new concept of query plans and a
QueryPlanCache to encapsulate the role that used to be filled by the
building and caching of the QueryTranslator arrays within
SessionFactory. This has a
Hibernate 3.1 rc2 has just been released. It contains some minor bug
fixes and changes to handling of connection release mode.
Please see the Change Log and Release Notes for more details:
http://sourceforge.net/project/shownotes.php?release_id=364170
The release can be downloaded at:
through the event listener system
(create-onflush tag)
I still need to test, but I'll be able to commit by the end of the
week-end
2. How does the type discovery work? Did you add a typeless
setParameter() to the Query?
Steve Ebersole wrote:
So as far as I am concerned, I am ready to push out
There maybe some setting we are just missing for test purposes. For
example, I don't know about you, but on my Oracle setup I disable
recovery logging on the datafiles backing my test schema. Without
disabling this option, it is painfully slow to run the testsuite against
Oracle; and obviously I
So as far as I am concerned, I am ready to push out 3.1rc2. Anything
anyone else wanted to get into this before I cut it?
I hope to get time to do it this weekend. If not, it'll be early next
week.
Here is the change-log so far:
** Bug
* [HHH-1045] - Example contains inner classes that
FYI,
I made the JDBCContext.hibernateTransaction field transient. This
worked around this issue of serializing a session with an associated
transaction, which also allowed me to expose more of the methods of
Session/SessionImplementor on the proxy generated from
ThreadLocalSessionContext.
Here's another concern with the current impl for
ThreadLocalSessionContext: the static accessors. Basically the way
this is setup right now, users will nt be able to use this
simultaneously for multiple session-factories...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
Of
Christian Bauer
Sent: Monday, October 03, 2005 9:25 AM
To: Hibernate development
Subject: Re: [Hibernate] ThreadLocalSessionContext javadoc inconsistency
Steve Ebersole wrote:
Here's another concern with the current impl for
ThreadLocalSessionContext: the static accessors. Basically the way
then
keep a map of SessionFactory - Session.
-Original Message-
From: Max Andersen
Sent: Monday, October 03, 2005 9:21 AM
To: Steve Ebersole; Hibernate development
Subject: Re: [Hibernate] ThreadLocalSessionContext javadoc inconsistency
On Mon, 03 Oct 2005 16:15:01 +0200, Steve Ebersole
Why? You can call clear() on collections marked as final. Obviously
you could not null them out...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Max
Rydahl Andersen
Sent: Tuesday, September 27, 2005 8:44 AM
To: Gavin King; Emmanuel Bernard
Cc:
A simpler solution would be to just add a writeObject() impl to
HibernateException which culls the cause if it is not serializable
(either to null or some marker).
This would be all encompassing. Plus it would still allow the cause to
be known (so long as no attempt is made to serialize it).
If you mean will we have 3.1 final out by the end of this week; no. We
are approximately 2 weeks away from 3.1rc1.
There is one change I am aware of that would cause problems with the
JBoss-Hibernate integration code regarding a change made to how
event-listeners are registered.
-Original
string format, just embed the date string.
UserVersionTypes might possibly even be doable. I'd have to think it
through a bit.
_
From: Gavin King
Sent: Saturday, August 13, 2005 5:39 PM
To: Steve Ebersole
Cc: hibernate-devel@lists.sourceforge.net
compared to my first example, right? I simply chose CDATA
tags to enclose my text, where you did not...
-Original Message-
From: Max Andersen
Sent: Tuesday, August 09, 2005 5:58 AM
To: Steve Ebersole; Hibernate devel
Subject: Re: [Hibernate] RE: testing question
i don't like database
5:58 AM
To: Steve Ebersole; Hibernate devel
Subject: Re: [Hibernate] RE: testing question
i don't like database-object, but I don't have a better suggestion,
so...(maybe just ddl ?)
I do though have some trimming suggestions:
database-object name=blahBlah
createCREATE INDEX .../create
drop
Of
Christian Bauer
Sent: Monday, August 08, 2005 1:55 PM
To: Hibernate devel
Subject: Re: [Hibernate] RE: testing question
On Aug 8, 2005, at 8:48 PM, Steve Ebersole wrote:
If anyone wants different name(s), speak now or forever hold your
peace...
I think it should have a name= attribute so
Let's move this discussion over to:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-840
-Original Message-
From: Max Andersen
Sent: Tuesday, August 09, 2005 5:58 AM
To: Steve Ebersole; Hibernate devel
Subject: Re: [Hibernate] RE: testing question
i don't like database
be the same issue...
-Original Message-
From: Max Andersen
Sent: Tuesday, August 09, 2005 5:58 AM
To: Steve Ebersole; Hibernate devel
Subject: Re: [Hibernate] RE: testing question
i don't like database-object, but I don't have a better suggestion,
so...(maybe just ddl ?)
I do though
for this.
-Original Message-
From: Max Andersen
Sent: Tuesday, August 09, 2005 2:32 PM
To: Steve Ebersole; Hibernate devel
Subject: Re: [Hibernate] RE: testing question
mainly for tooling.
/max
Why a name, though? I was not planning on allowing lookup of these
things as I don't see a benefit
huh? we have no table/ element...
I'll check it in like this. If you feel that strongly about it, feel
free to change it.
-Original Message-
From: Max Andersen
Sent: Tuesday, August 09, 2005 2:20 PM
To: Steve Ebersole; Hibernate devel
Subject: Re: [Hibernate] RE: testing question
In working on this functionality to test the support for database
generated values, I ran across an interesting issue with unit testing
this functionality. Basically, the only real way to test this in a
consistent fashion across all databases is to apply triggers to the
database in use for
1 - 100 of 144 matches
Mail list logo
