Does anyone think this is a bad idea? Seems simple and a good idea to
me but it is changing an exported format.
Kathey Marsden (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-1547?page=all ]
Kathey Marsden updated DERBY-1547:
----------------------------------
Urgency: Normal (was: Low)
Changing this to Normal Urgency. It would be a huge supportability improvement,
and can only happen in a feature release, so it would be good to get in now.
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
Priority: Minor
Fix For: 10.2.0.0
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.
