db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Trivial Update of "TriggerImplementation" by DanDebrunner
Date Wed, 26 Apr 2006 23:41:41 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by DanDebrunner:
http://wiki.apache.org/db-derby/TriggerImplementation

------------------------------------------------------------------------------
   * The VTI classes implement java.sql.!ResultSet directly and wrap a !ResultSet obtained
from the embedded JDBC driver. This has performance and functionality impact. The !TriggerOldTransitionRows
and !TriggerNewTransitionRows classes must be updated to match each JDBC release, currently
they are stuck at JDBC 1.2. Changing them to implement java.sql.!PreparedStatement would mean
they could instead return the wrapped !ResultSet directly. For example getBlob is not currently
supported for statement triggers.
   * Any access to any column in a row trigger requires going through getObject, thus creating
Objects for every value.
   * Accessing multiple columns leads to multiple accesses getNewRow() and/or getOldRow()
methods.
-  * (NEED TO VERIFY) Since accessing columns is through JDBC for row triggers, columns with
identical upper-cased names are not handled correctly.
+  * [http://issues.apache.org/jira/browse/DERBY-1258 DERBY-1258] Since accessing columns
is through JDBC for row triggers, columns with identical upper-cased names are not handled
correctly.
  

Mime
View raw message