I'm not from the Hibernate team but, although "the cost to create a users
mailing list is essentially nothing", the cost to read and response to it in
addition to the forum is very expensive...
They could surely create a user-list but they won't probably listen to it
and you won't get any answer.
Sorry, but if you post a question to the forum, you will receive a
notification if someone else answer it...
Please check your account settings and your email address on the forum.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: me
Title: Message
Hi
there,
Just noticed the
CharacterType does not extend ImmutableType (as StringType for
example).
As a
java.lang.Character is *not* mutable, I though the CharacterType sould be
Immutable as well... Am I wrong somewhere ?
-bertrand
smime.p7s
Description: S/MIME cryptog
Title: Message
The
ProxoolConnectionProvider has changed since Hibernate version 2.1.4 - mainly due
to issue HB-987.
The bigest impact of
those changes is it is now impossible to configure Proxool via properties
embedded in the hibernate.properties files. Too bad - it was a nice feature
(
> I think the MS Driver is actually the Data-Direct driver. You
> could file a bug report with them and it might get fixed faster.
>
You are right - but the MS version is not the latest shipped by
DataDirect...
[...]
DataDirect Technologies provides an OEM version of its JDBCR SQL Server
driver
Dear all,
I have recently *discovered* the usage of the all-delete-orphan cascade
directive and decided to give it a try.
So I removed my own implementation and let Hibernate delete the orphans for
me.
To my great surprise, Hibernate was slower than my own code by a factor of
60% ?!?
For the comp
For those who are intrested, the issues are: HB663 & HB664
(will see this time how long it takes for this mail to go thru the mailing
list ;-)
> -Original Message-
> From: Gavin King [mailto:[EMAIL PROTECTED]
> Sent: jeudi 29 janvier 2004 22:48
> To: Bertrand Renuart
Dear developpers/maintainers,
I was wondering were I should report issues regarding the Hibernate test
cases... Should I post a mail to the dev mailing list or should I post an
entry in JIRA ?
If the JIRA solution is the prefered approach, it might be a good idea to
add a 'TestCase' component to
Dear all,
I noticed the method net.sf.hibernate.util.next() may fail under some
circumstances.
I have not encountered any situation (yet) where this happens, but the code
is not robust enough and a simple test case (on this class) can break it.
Here is the current code:
public Object nex
Title: Message
MasterDetailTest.testPolymorphicCriteria() fails - at least in my
case.
This test makes a
polymorphic query for all persistent instances that derive from
java.lang.Object.
It expects a result
of two - created just before.
Unfortunately, at
this stage, the database contain
Dear all,
I just noticed FooBarTest.testNamedParams() fails under MS SQLServer.
The breaking code is:
if (! (getDialect() instanceof Oracle9Dialect) ) { // oracle barfs on "x
in ()"
q.setParameterList("nameList", Collections.EMPTY_LIST);
list = q.list();
assertTrue( list
In this case, the current README.TXT is easier to read !
The version in the filename is certainly the easiest and safer (less error
prone) solution.
+1 on version in filename
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Christian Bauer
> Sen
12 matches
Mail list logo
