[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-197) Session-less HQL

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Wed, 16 Jul 2003 9:41 AM

We have discussed this issue over and over again. Hibernate now provides

(1) Session.evict() method
(2) Session.setFlushMode(FlushMode.NEVER)

I personally think that is sufficient.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-197


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-197
    Summary: Session-less HQL
       Type: New Feature

     Status: Closed
   Priority: Major
 Resolution: DUPLICATE

    Project: Hibernate2

   Assignee: 
   Reporter: Andrea Aime

    Created: Wed, 16 Jul 2003 3:04 AM
    Updated: Wed, 16 Jul 2003 9:41 AM

Description:
There are pieces of code in the application that load or save huge quantities of data but don't really need session management, yet having the ability to use OR mapping is nice for code uniformity and to leverage Hibernate prepared statements caching and batching. The main limiting point is that using HQL attachs the object to the sessions, which may be unecessary work when you don't modify the objects after loading or saving, and fills up the memory (one of my apps easily triggered out of memory exceptions because of it, and I had to convert the code to a more complex direct jdbc...)


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira