[ http://issues.apache.org/jira/browse/DERBY-1547?page=comments#action_12428408 ] Kathey Marsden commented on DERBY-1547: ---------------------------------------
Looking back at your original post asking about using the sed test harness capability, if you go that route. I do not think adding a global pattern to Sed.java is a safe thing to do. One thing I always wondered was why we need to test the same metadata calls in so many tests. If we just tested it in one place, you would need only one sed file for jdbc and one for odbc. But I am not sure of the reasons why we test the same calls so many times. I think I can safely say NSInSameJVM doesn't need it. > 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
