Re: [Hibernate] Oracle error: exceeded simultaneous SESSIONS_PER_USER limit

Hi Matt, From your example code that you posted, it doesn't seem like you were ever closing the sessions you opened. Is this true, or are you perhaps doing it somewhere else in your code? The way that I handle Hibernate sessions in all of my applications is to use a ServletFilter that open

[Hibernate] Hibernate Thread Local Session and JUnit

I am using the Thread Local Session Design Pattern as documented at: http://hibernate.bluemars.net/42.html This worked great in my web application when running through Tomcat. Tomcat uses Commons DBCP for connection pooling. The old way I was doing it - now obviously kludgy - was to create a ne

Re: [Hibernate] Oracle error: exceeded simultaneous SESSIONS_PER_USER limit

I *think* I fixed this problem by implementing a Connection Pool in Tomcat and configuring Hibernate with a HibernationSession (using ThreadLocal) and talking to Oracle using that method. Seems to only open one connection now. Thanks, Matt > I'm getting the following error when using Hibernate

[Hibernate] Oracle error: exceeded simultaneous SESSIONS_PER_USER limit

I'm getting the following error when using Hibernate as my persistence layer: java.sql.SQLException: ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit ORA-02063: preceding line from NAS_AC_72 ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit ORA-02063: preceding line from NAS_AC_72

[Hibernate] sorted collection

I have 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"   My mapping is :       ...                     .. ...   and My jav

Re: [Hibernate] Hibernate 2

forgot one... >* Remove the exception that occurs if you save an object > that is already associated with the session. This > makes save() consistent with saveOrUpdate(). >I am probably a +1 on this I would suggest the same mechanism as with delete - it is nice to have it as an option. /max

Re: [Hibernate] Using CLOBs

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(f

Re: [Hibernate] Hibernate 2

hey all and happy new year Gavin King wrote: 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

Re: [Hibernate] Hibernate 2

> Please vote on the following proposals: > > * Rename the 'role' attribute to 'name' in all > collection > elements in the new DTD, for consistency with > , >and elements. The role attribute > no longer > has any extra semantics beyond being a simple > property > name. > > I am +1 +

Re: [Hibernate] Hibernate 2

On 02 Jan (10:20), Gavin King wrote: > In the new DTD, I have also renamed the 'readonly' attribute > to 'inverse', since its name was causing all kinds of confusion > for new (and not-so-new) users. +1 :) > * Rename the 'role' attribute to 'name' in all collection > elements in the new DTD,

Re: [Hibernate] Length of Hibernate-generated aliases in SQL

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

RE: [Hibernate] Length of Hibernate-generated aliases in SQL

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

Re: [Hibernate] Length of Hibernate-generated aliases in SQL

Could you give an hbm.xml and query example that gives that error ? (it would be nice to have some test scenario :) (especially, since it would be nice to know what one could do to avoid such a thing- it would also be a problem on db2 since it also has some "weird" low limitations) /max Yi

RE: [Hibernate] Length of Hibernate-generated aliases in SQL

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 tric

[Hibernate] Hibernate 2

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 modu

RE: [Hibernate] Using CLOBs

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); tx.commit();