Right. The issue is we can't have the infinite web of project
implementation details leaking to users unncessarily. Hibernate is a
little different in that its used both in Java SE and Java EE profiles.
My concern is that a pure Java EE client should not care about that
antlr happens to be used for
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 p
On Wed, 08 Feb 2006 15:51:49 +0100, Steve Ebersole
<[EMAIL PROTECTED]> wrote:
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.
Fair reasoning.
/max
-Original Message-
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-dev
Hi,
antlr exceptions can probably be "contained" by some of the methods
mentioned below - no problem.
I'm just wondering what to do with other exceptions ? They will have the
same/similar problem correct? e.g. a ocracle driver specific exception
occurs
which is pretty good to have as the cause
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 perhaps
> which it isn't afaik. the antlr version started to include
> more data in the exception over time.
>
Including additional data is not an incompatible serialzable change
generally. Its optional data that will be ignored and cannot affect the
legacy implementation.
> >> calling printStackTrace(
This is planned for Hibernate 3.2
Bill Burke wrote:
Can we have a default HEM key generator that will not force an insert
when using FlushMode.NEVER? Like Table or Sequence or some other
hibernate specific generator?
I've been working through some example applications for my book and am
fin
Hello,
The livelink product handles n to n relationship without intermediate table but
with a field with multiple values. Is it possible to instruct Hibernate to
comply to this? if so how do I do it? via the dialect?
Regards,
Ced.
Message d'origine
De: Ste
