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 2007/07/24 19:46:31 UTC
[jira] Commented: (DERBY-2966) rs.moveToInsertRow() causes loss of
connection with TERRITORY_BASED collation.
[ https://issues.apache.org/jira/browse/DERBY-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515044 ]
Mamta A. Satoor commented on DERBY-2966:
----------------------------------------
Commited a patch in main (Revision: 559125) and migrated it into 10.3 codeline (Revision: 559133) . Commit comments were as follows
DERBY-2966
We need to have context set up inside a moveToInsertRow code because that code tries to do DTD.getNull and getNull needs to find RuleBasedCollator which is found by relying on the context. Putting the context fixed the problem.
> rs.moveToInsertRow() causes loss of connection with TERRITORY_BASED collation.
> ------------------------------------------------------------------------------
>
> Key: DERBY-2966
> URL: https://issues.apache.org/jira/browse/DERBY-2966
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.0.0
> Reporter: Kathey Marsden
> Assignee: Mamta A. Satoor
> Priority: Critical
> Fix For: 10.3.1.4, 10.4.0.0
>
> Attachments: NoConnectionBug.java
>
>
> In the attached test case, rs.moveToInsertRow() causes loss of the connection with a TERRITORY_BASED collation database. With UCS_BASIC it is fine.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.