[ http://issues.apache.org/jira/browse/DERBY-1547?page=all ]
V.Narayanan updated DERBY-1547:
-------------------------------
Attachment: DERBY-1547-sed.diff
DERBY-1547-sed.stat
Hi,
NOTE: I AM YET TO RUN derbyall ON THE PATCH AND IT IS NOT MEANT FOR A COMMIT
I had run derbyall prior in order to find out possible test failures with this
change so that I can fix the test master files. I have fixed the master files
but have to again run derbyall after this change. I however thought I should
post the patch so that you could give ur comments on it.
Pls note that the subversion number that would be displayed has been replaced
with a pattern -(EXPECTED SUBVERSION NUMBER)
I hope to finish running derbyall by tommorrow and post a final patch by
tommorrow. In the mean time please do give me ur comments on any possible issue
that u think might be present in this patch.
thanx
Narayanan
> 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.1.0
>
> Attachments: DERBY-1547-sed.diff, DERBY-1547-sed.stat,
> 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
