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 "Ole Solberg (JIRA)" <ji...@apache.org> on 2008/11/24 09:29:44 UTC

[jira] Closed: (DERBY-2807) Create a test for BlobClob compatibility on Derby server versions vs. Derby client versions.

     [ https://issues.apache.org/jira/browse/DERBY-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ole Solberg closed DERBY-2807.
------------------------------

    Resolution: Fixed

Was completed....

> Create a test for BlobClob compatibility on Derby server versions vs. Derby client versions.
> --------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2807
>                 URL: https://issues.apache.org/jira/browse/DERBY-2807
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.3.1.4
>            Reporter: Ole Solberg
>            Assignee: Ole Solberg
>            Priority: Minor
>         Attachments: compatibilitytest.properties, derby-2807-v1.diff.txt, derby-2807-v2.diff.txt
>
>
> Run '..../tests/jdbcapi/BlobClob4BlobTest.java' in the 'java/testing/org/apache/derbyTesting/functionTests/tests/junitTests/compatibility/CompatibilityCombinations.java' framework to test combinations of Derby server versions vs. Derby client versions. The CompatibilityCombinations framework also allows varying the JVM version used on the server and client side.

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