[ http://issues.apache.org/jira/browse/DERBY-1547?page=all ]
V.Narayanan updated DERBY-1547:
-------------------------------
Attachment: DERBY-1547_v1.diff
DERBY-1547_v1.stat
Hi,
Attached are the patches for this issue. I HAVE NOT run derbyall on the whole
patch as yet.
1) I ran derbyall first after making changes to embedded side
2) fixed the issues in tests that failed(all these tests were in jdbcapi).
3) Ran jdbcapi on embedded side. All of these tests passed.
4) Made changes to Client side
5) Ran tests that had failed on embedded side alone. These passed.
My expectation is that no tests should fail in this patch. But will anyway run
derbyall and submit another patch tomorrow. I thought I could the patches up
for review anyway.
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.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
