It's an issue a collegue of mine entered some times ago (HBI-31). But it
wasn't well explained (and initially wasn't talking about hibernate 2 so
don't even read it, it will makes things harder to explain).
But anyway. I'm talking about the fact that hibernate is causing constraint
violations if a
On Jul 21, 2004, at 10:42 PM, Henri Tremblay wrote:
Does this remove the hibernate limitation on nullable foreign keys?
(that
foreign keys of collections need to be nullable even if there is a
cascade
all-delete-orphan). If yes, great! If no, still great! (but I'll be
back on
this issue).
What?
Does this remove the hibernate limitation on nullable foreign keys? (that
foreign keys of collections need to be nullable even if there is a cascade
all-delete-orphan). If yes, great! If no, still great! (but I'll be back on
this issue).
Henri
- Original Message -
From: "Gavin King" <[EM
On 21 Jul (02:57), Gavin King wrote:
> So, let's stay focussed, and get this thing done!
I guess we should open a new HB3 project on JIRA or make TODO public.
--
Christian Bauer
+49 171 455 66 53
Hibernate
[EMAIL PROTECTED]
http://hibernate.org
JBoss Inc
[EMAIL PROTECTED]
http://jboss.com
-
OK, we are now very close to a 3.0 alpha release.
The remaining major issues for 3.0 are:
TODO-12: Support for regional and temporal data
TODO-86: EJB 3.0 style create() and merge()
TODO-74: Lazy property-level fetching
TODO-28: New HQL parser
TODO-81: Enable batch updates for versioned data
TODO-1
