Return-Path: Delivered-To: apmail-ibatis-user-java-archive@www.apache.org Received: (qmail 88608 invoked from network); 17 Sep 2006 15:51:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 17 Sep 2006 15:51:23 -0000 Received: (qmail 17952 invoked by uid 500); 17 Sep 2006 15:51:22 -0000 Delivered-To: apmail-ibatis-user-java-archive@ibatis.apache.org Received: (qmail 17549 invoked by uid 500); 17 Sep 2006 15:51:21 -0000 Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user-java@ibatis.apache.org Delivered-To: mailing list user-java@ibatis.apache.org Received: (qmail 17538 invoked by uid 99); 17 Sep 2006 15:51:21 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Sep 2006 08:51:21 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of lists@nabble.com designates 72.21.53.35 as permitted sender) Received: from [72.21.53.35] (HELO talk.nabble.com) (72.21.53.35) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Sep 2006 08:51:09 -0700 Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1GOyuo-0008LL-PV for user-java@ibatis.apache.org; Sun, 17 Sep 2006 08:50:42 -0700 Message-ID: <6351220.post@talk.nabble.com> Date: Sun, 17 Sep 2006 08:50:42 -0700 (PDT) From: soussou97 To: user-java@ibatis.apache.org Subject: Re: Analyze of a Blob In-Reply-To: <16178eb10609162148h335ca5c1t5d32d1715e9a105b@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: dboussebha@yahoo.fr References: <6344974.post@talk.nabble.com> <16178eb10609162148h335ca5c1t5d32d1715e9a105b@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi Clinton; Yes I have mapped directly to a byte[] with iBATIS (no problem) => I get well and correctly the blob via Ibatis. But My question is how analyze the byte array for extracting the data which contains. Yes my blob into the database is very big (about 20 Mo) but I must from of these data to fill of the objects. Why use directly jbdc instead of ibatis ? Ibatis is not adapted to treat the blob of important size (performance problem) ? Can you give me more details. Ragards; Clinton Begin wrote: > > I wouldn't use readFUlly() unless you know for sure the data is very > small. > If so, you should be able to map it directly to a byte[] with iBATIS. > > If the data is big, I'd suggest streaming it to a temporary file for use. > In this case, you might want to bypass iBATIS and use JDBC directly. > > > Cheers, > Clinton > > > On 9/16/06, soussou97 wrote: >> >> >> Hi; >> >> I use Ibatis for getting a field BLOB I must transcribe the data which >> contains, for example: with the position from 0 to 10 I get of the dates, >> position 10 to 15 32-integer, etc... (with the constraint of the size of >> the >> BLOB which is very important). >> I think of doing this: I have my attribute: >> byte [ ] data; >> DataInputStream in = nex DataInputStream(new >> ByteArrayInputStream(data)) >> Next, I use in.readFully(data, pos, len) to retreive the data. >> its the best implementation or not ? Have you a example ? >> >> Regards; >> >> >> -- >> View this message in context: >> http://www.nabble.com/Analyze-of-a-Blob-tf2284043.html#a6344974 >> Sent from the iBATIS - User - Java forum at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/Analyze-of-a-Blob-tf2284043.html#a6351220 Sent from the iBATIS - User - Java forum at Nabble.com.