[DERBY-2345] truncate on a Blob does not work when the Blob is in memory

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 10.3.1.4
• Component/s: JDBC
• Assignee: Anurag Aggarwal
• Reporter: V.Narayanan
• Created: 16/Feb/07 12:39
• Updated: 10/Sep/08 05:56
• Resolved: 19/Feb/07 23:20

Description

I tried the following repro. After calling the truncate the Blob object still returns the length as 29 (its original length) .

import java.sql.*;

public class TruncateBugRepro {

Connection con = null;

public Connection getEmbeddedConnection() throws Exception {
if(con == null)

{ Class.forName("org.apache.derby.jdbc.EmbeddedDriver"); con = DriverManager.getConnection ("jdbc:derby:DB1;create=true"); }

return con;
}

public void testTruncate() throws Exception

{ //String used to getBytes from and insert into Blob. String str = new String("I am a Blob!!! I am a Blob!!!"); Connection con = getEmbeddedConnection(); //create the blob Blob blob = con.createBlob(); //insert bytes blob.setBytes(1,str.getBytes()); //Retuns the Blob length as 29 System.out.println("" + blob.length()); blob.truncate(14); //returns the Blob length as 29 System.out.println("" + blob.length()); }

public static void main(String[] args) throws Exception

{ TruncateBugRepro t = new TruncateBugRepro(); t.testTruncate(); }

}

Issue Links

• is related to: DERBY-2247 provide set methods for blob in embeded driver