Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <2140040412.1219760564836.JavaMail.jira@brutus>
Date: Tue, 26 Aug 2008 07:22:44 -0700 (PDT)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Created: (DERBY-3853) Behaviour of setTypeMap() differs
 between embedded and client
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Behaviour of setTypeMap() differs between embedded and client
-------------------------------------------------------------

                 Key: DERBY-3853
                 URL: https://issues.apache.org/jira/browse/DERBY-3853
             Project: Derby
          Issue Type: Improvement
          Components: JDBC, Newcomer
    Affects Versions: 10.5.0.0
            Reporter: Knut Anders Hatlen
            Priority: Minor


On the embedded driver, Connection.setTypeMap() behaves like this (when the connection is not closed):

  - if the map argument is null, throw an SQLException with SQLState XJ081

  - if the map is not null and not empty, throw an SQLException with SQLState 0A000

  - if the map is not null and empty, do nothing

The behaviour on the client driver is this:

  - always throw an SQLException with SQLState 0A000

We should try to make the two drivers behave the same way when setTypeMap() is called. (This would also allow us to simplify some of the tests in J2EEDataSourceTest).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.