db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2984) improve XML.setValueFromResultSet() to not require reparse in cases where it could "know" value was already parsed.
Date Tue, 31 Jul 2007 23:05:53 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mike Matrigali updated DERBY-2984:
----------------------------------

    Summary: improve XML.setValueFromResultSet() to not require reparse in cases where it
could "know" value was already parsed.  (was: imporove XML.setValueFromResultSet() to not
require reparse in cases where it could "know" value was already parsed.)

> improve XML.setValueFromResultSet() to not require reparse in cases where it could "know"
value was already parsed.
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2984
>                 URL: https://issues.apache.org/jira/browse/DERBY-2984
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Mike Matrigali
>            Priority: Minor
>
> During trigger processing XML.setValueFromResultSet() is called.  It currently will reparse
the string coming in to determine if it is a valid XML to set it's
> type appropriately.  In some cases this is being called when the old  value that was
previosly stored is being created, and the system could "know" that
> parse is not needed.  Not sure if more support in the storage of the xml type would be
needed or maybe changes in the interface.  
> See DERBY-2350 for more discussion on this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message