[
https://issues.apache.org/jira/browse/DERBY-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-1098:
----------------------------------
Urgency: Low
Labels: derby_triage10_8 (was: )
Triage for 10.8. I tend to think the client should at be at least as
pessimistic as embedded, but don't know if embedded is being too pessimistic.
> isDefinitelyWritable on client returns true where embedded returns false
> ------------------------------------------------------------------------
>
> Key: DERBY-1098
> URL: https://issues.apache.org/jira/browse/DERBY-1098
> Project: Derby
> Issue Type: Bug
> Components: JDBC, Network Client
> Affects Versions: 10.2.1.6
> Environment: Solaris 10/x86, Sun Java 1.4.2
> Reporter: Dag H. Wanvik
> Priority: Minor
> Labels: derby_triage10_8
>
> ResultSetMetaData#isDefinitelyWritable on the client does the same test
> as isWritable.
> The embedded driver is more pessimistic, and always returns false.
> The comment is the embedded code says:
> // we just don't know if it is a base table column or not
> For the present implementation of updatable result set (forward only), under
> which conditions would the update fail? Or is the client correct correct here?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
