[
http://issues.apache.org/jira/browse/DERBY-1547?page=comments#action_12428985 ]
V.Narayanan commented on DERBY-1547:
------------------------------------
Possible solution
-----------------
1) Find out in the tests where the input stream returned upon starting the
NetworkServer is being
flushed.
2) Instead of flushing this input stream directly pass it on to a Util class
that will search for
the subversion number pattern in the stream and
2.a) Check if the pattern is right
2.b) Remove the pattern and return the pattern string
2.b.1) So JDBC Driver 'Apache Derby Embedded JDBC Driver', version 10.3
(10.3.0.0 alpha -
(344567M)) would be replaced by
Apache Derby Embedded JDBC Driver', version 10.3 (10.3.0.0
alpha)
3) Find the place where the getDatabaseProductVersion and getDriverVersion o/p
are being printed.
Again search and replace the subversion number.
> 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_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
