db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John H. Embretsen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1547) Add svn version number to DatabaseMetaData getDatabaseProductVersion and getDriverVersion() to improve supportability
Date Wed, 04 Oct 2006 08:01:20 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1547?page=comments#action_12439758 ] 
John H. Embretsen commented on DERBY-1547:

When using the "primary" release (i.e. the -src distribution, built by the user),
12 tests in derbyall fail because we forgot to have the seding patterns (added for this Jira
issue) to also match the word "exported" instead of the SVN revision number:


Example diff:

********* Diff file derbyall/derbylang/metadata.diff
*** Start: metadata jdk1.6.0-rc derbyall:derbylang 2006-10-03 16:40:26 ***
16 del
< JDBC Driver 'Apache Derby Embedded JDBC Driver', version 10.2 ( -(EXPECTED SUBVERSION
> JDBC Driver 'Apache Derby Embedded JDBC Driver', version 10.2 ( - (exported))
152 del
< getDatabaseProductVersion(): -(EXPECTED SUBVERSION INFO)
153 del
< getDriverVersion(): -(EXPECTED SUBVERSION INFO)
> getDatabaseProductVersion(): - (exported)
> getDriverVersion(): - (exported)
Test Failed.
*** End:   metadata jdk1.6.0-rc derbyall:derbylang 2006-10-03 16:40:40 ***

This is clearly not important to fix for the current ( RC, but we should try to fix
it before the next release or RC.

> 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:
>            Reporter: Kathey Marsden
>         Assigned To: V.Narayanan
>            Priority: Minor
>             Fix For:
>         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. " - (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


View raw message