[jira] Resolved: (DERBY-1547) Add svn version number to DatabaseMetaData getDatabaseProductVersion and getDriverVersion() to improve supportability

["Myrna van Lunteren (JIRA)" <ji...@apache.org>]

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

Myrna van Lunteren resolved DERBY-1547.
---------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 10.3.0.0)
                   10.2.1.6

Apart from the issue reported  last it appears this bug was fixed in 10.2.1.6.
Even the last issue must've gotten fixed at some point because we don't see that failure anymore. As there's no further disucssion of that fix here I'm disregarding that for the fix version for this bug & adding 10.2.1.6.

> Add svn version  number to DatabaseMetaData getDatabaseProductVersion and getDriverVersion()  to improve supportability
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1547
>                 URL: https://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.1.6
>
>         Attachments: DERBY-1547-sed-v1.diff, DERBY-1547-sed-v1.stat, DERBY-1547-sed-v2.diff, DERBY-1547-sed-v2.stat, DERBY-1547-sed-v3.diff, DERBY-1547-sed-v3.stat, DERBY-1547-sed.diff, DERBY-1547-sed.stat, DERBY-1547_v1.diff, DERBY-1547_v1.stat, derbyall_fail.txt
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.