You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2012/10/02 06:43:07 UTC
[jira] [Updated] (DERBY-2984) improve XML.setValueFromResultSet()
to not require reparse in cases where it could "know" value was already
parsed.
[ https://issues.apache.org/jira/browse/DERBY-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mamta A. Satoor updated DERBY-2984:
-----------------------------------
Urgency: Normal
Labels: derby_triage10_10 (was: )
> 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
> Labels: derby_triage10_10
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira