Bug 109010 - No access to APIs for streaming of LOBs into the DB
Summary: No access to APIs for streaming of LOBs into the DB
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Web Application Framework
Classification: Retired
Component: persistence
Version: nightly
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: ccm-bugs-list
QA Contact: Jon Orris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-11-04 10:49 UTC by Daniel Berrangé
Modified: 2007-04-18 16:59 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-09-02 17:27:32 UTC
Embargoed:


Attachments (Terms of Use)

Description Daniel Berrangé 2003-11-04 10:49:43 UTC
Description of problem:

All common JDBC drivers provide APIs for streaming of LOBs in & out of
the DB. These APIs, however, are not exposed/used by persistence, so
applications have to pull the entire LOB into memory when
reading/writing. This is not at all good for scalability of
applications using LOBs, such as CMS images / file attachments / Doc
Manager. A mere 10 users downloading 35 MB files will use up at *best*
350 MB, potentially some multiple of this amount if the byte[] are
copied in memory ever. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Daniel Berrangé 2006-09-02 17:27:32 UTC
Closing old tickets



Note You need to log in before you can comment on or make changes to this bug.