Max, it would happen whenever you have a column name that approaches
the limit for the database. Hibernate needs to add an _0, etc at
the end when rendering aiases.
-Original Message-
From: max [mailto:[EMAIL PROTECTED]
Sent: Thursday, 2 January 2003 6:11 PM
To: Hibernate Mailing
Gavin King wrote:
Max, it would happen whenever you have a column name that approaches
the limit for the database. Hibernate needs to add an _0, etc at
the end when rendering aiases.
I know, would just be easier if he got a clean example :)
But Ok - I've fought with these kind of troubles before
Well, I imported the Hibernate2 sourcetree last night. Its in
its own module which means that for the next couple of months
we need to be *very* careful about handling patches. Bugfixes
and minor improvements must be applied against *both* trees.
(New features need only go into the Hibernate2
Ihave 2
classes.
The first class
contains a collection of the second class.
I want the
collection is sorted but, when I return the collection,I have an error
"Failed to lazily initialize a collection"
Mymapping is
:
class name="Class1" table="table1"
...
set role="child" lazy="true"
Yick. The biggest design problem with Hibernate at present is
the fact that we have no single class responsible for rendering
SQL. (As I have mentioned before, Hibernate models SQL
statements using StringBuffer...) So little things like this
that should be *very* easy turn out to be way more
Gavin King wrote:
A the 4000 characters bit is where you start to need
the for update clause. We were wondering about that
earlier. I think you *could* make it work like this:
s = sf.openSession();
tx = s.beginTransaction();
foo = new Foo();
foo.setClob( Hibernate.createClob() );
s.save(foo);
