Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Mon, 14 Feb 2011 21:34:02 +0000 (UTC)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <371804153.15861.1297719242825.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Updated: (DERBY-1098) isDefinitelyWritable on client returns
 true where embedded returns false
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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