Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 24490 invoked from network); 2 Jul 2005 00:14:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Jul 2005 00:14:54 -0000 Received: (qmail 47419 invoked by uid 500); 2 Jul 2005 00:14:53 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 47378 invoked by uid 500); 2 Jul 2005 00:14:53 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 47365 invoked by uid 99); 2 Jul 2005 00:14:52 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Jul 2005 17:14:52 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [32.97.182.145] (HELO e5.ny.us.ibm.com) (32.97.182.145) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Jul 2005 17:14:54 -0700 Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e5.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id j620EklZ011103 for ; Fri, 1 Jul 2005 20:14:46 -0400 Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay02.pok.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id j620EkZe263026 for ; Fri, 1 Jul 2005 20:14:46 -0400 Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.12.11/8.13.3) with ESMTP id j620Ejpo015145 for ; Fri, 1 Jul 2005 20:14:45 -0400 Received: from [127.0.0.1] (sig-9-48-115-201.mts.ibm.com [9.48.115.201]) by d01av01.pok.ibm.com (8.12.11/8.12.11) with ESMTP id j620EiQu015123 for ; Fri, 1 Jul 2005 20:14:45 -0400 Message-ID: <42C5DC72.3070106@debrunners.com> Date: Fri, 01 Jul 2005 17:14:42 -0700 From: Daniel John Debrunner User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Derby Development Subject: Re: [jira] Created: (DERBY-438) Update triggers on tables with blob columns fail at execution time if the triggered-SQL-statement references the blob column(s). References: <183491813.1120259759312.JavaMail.jira@ajax.apache.org> In-Reply-To: <183491813.1120259759312.JavaMail.jira@ajax.apache.org> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N A B (JIRA) wrote: > Update triggers on tables with blob columns fail at execution time if the triggered-SQL-statement references the blob column(s). I'm suprised this is not documented, BLOB and CLOB columns do not work with triggers. This is because within the database engine, there is no mechanism to create a java.sql.Blob object (or Clob) from a SQL BLOB (CLOB) datatype. The java.sql.Blob returned from a ResultSet is handled at the JDBC layer, not within the engine. This is the same reason as to why BLOB and CLOB types cannot be passed into a method or function. Dan.