Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #227 (closed)

Opened 18 years ago

Closed 18 years ago

Evaluate HQL batch updates for Events and other non-used objects

Reported by: jamoore Owned by: jamoore
Priority: minor Milestone: 3.0-M3
Component: General Version: 3.0-M2
Keywords: performance, hibernate, hql, iteration5 Cc:
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description

Hibernate provides batch updates of the form:

  • INSERT INTO ... SELECT ...
  • ( UPDATE | DELETE ) FROM? EntityName? (WHERE where_conditions)?

For some use cases where the instances are never used in the JVM (Events, EventLogs, etc.) this may be more peformant.

See http://www.hibernate.org/hib_docs/v3/reference/en/html/batch.html for more.

Change History (1)

comment:1 Changed 18 years ago by jmoore

  • Keywords iteration5 added
  • Milestone changed from Unscheduled to 3.0-M3
  • Resolution set to fixed
  • Status changed from new to closed

Completed by #328.

Summary :

  • Batch doesn't work for events because INSERT INTO ... SELECT ... has definiciences.
  • Stateless session, though difficult, can be used with care. However, we had to get rid of embedded components (details, e.g.)
Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.68143 sec.)

We're Hiring!