Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <643935424.1142015439257.JavaMail.jira@ajax>
Date: Fri, 10 Mar 2006 18:30:39 +0000 (GMT)
From: "Dag H. Wanvik (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Created: (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

isDefinitelyWritable on client returns true where embedded returns false
------------------------------------------------------------------------

         Key: DERBY-1098
         URL: http://issues.apache.org/jira/browse/DERBY-1098
     Project: Derby
        Type: Bug
  Components: JDBC, Network Client  
    Versions: 10.2.0.0    
 Environment: Solaris 10/x86, Sun Java 1.4.2
    Reporter: Dag H. Wanvik
    Priority: Minor


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.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira