Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <17015174.1155742154977.JavaMail.jira@brutus>
Date: Wed, 16 Aug 2006 08:29:14 -0700 (PDT)
From: "Deepa Remesh (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-1547) Add svn version  number to
 DatabaseMetaData getDatabaseProductVersion and getDriverVersion()  to
 improve supportability
In-Reply-To: <11729882.1153401073826.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DERBY-1547?page=comments#action_12428414 ] 
            
Deepa Remesh commented on DERBY-1547:
-------------------------------------

Narayanan, Sorry for the confusion. I had seen the same failures which you reported when I ran derbyall in the new trunk but now I realize those failures had a different diff. And I mixed this with your report thinking you are reporting the same diffs. So my previous comment is not valid.

Just want to add that NSinSameJVM is testing the message printed out by Network server at startup and shutdown. This was added as part of DERBY-515. 

> Add svn version  number to DatabaseMetaData getDatabaseProductVersion and getDriverVersion()  to improve supportability
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1547
>                 URL: http://issues.apache.org/jira/browse/DERBY-1547
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>    Affects Versions: 10.1.3.2
>            Reporter: Kathey Marsden
>         Assigned To: V.Narayanan
>            Priority: Minor
>             Fix For: 10.2.0.0
>
>         Attachments: DERBY-1547_v1.diff, DERBY-1547_v1.stat
>
>
> getDatabaseProductVersion and getDriverVersion() report only the four digit Derby version number and not the svn build number.   It would be useful to return  the full version including the build number  as sysinfo does: e.g. "10.1.2.4 - (392472)", That way it will be clear from application logs that collect this information exactly what revision level they are running if they are using rolled up fixes on the maintenance branch between releases.
> There may be risk in doing this however if applications are parsing the version information, but hopefully they will use getDatabaseMajorVersion() , getDatbaseMinorVersion, getDriverMajorVersion, and getDriverMinorVersion for such proccessing.  

-- 
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