db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1547) Add svn version number to DatabaseMetaData getDatabaseProductVersion and getDriverVersion() to improve supportability
Date Mon, 14 Aug 2006 02:46:14 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1547?page=comments#action_12427793 ] 
            
V.Narayanan commented on DERBY-1547:
------------------------------------

Hi,

contrary to my expectations there were quite a few failures in the tests. Most of the failures
are due to the following


< Apache Derby Network Server - 10.3.0.0 alpha started and ready to accept connections
on port 20000 at xxxxxxFILTERED-TIMESTAMPxxxxxGMT
2a2
> Apache Derby Network Server - 10.3.0.0 alpha - (431279M) started and ready to accept
connections on port 20000 at xxxxxxFIL

I have failures in the Upgrade_10_1_10_2 test as well. It fails because of a caseVersion check.
I haven't looked at this in detail. But a look at the out files suggested that pattern replacement
in not the solution to these.

10.3.0.0 alpha has been replaced by 10.3.0.0 alpha - (431279M) in the current patch. According
to me the following are the ways available to resolve this issue

1) Adding a  _sed.properties to each of these tests. But this results in the following _sed.properties
files
     metadata_sed.properties            (which was already present)
     odbc_metadata_sed.properties (which was already present)
     dbMetaDataJdbc30_sed.properties
     NSinSameJVM_sed.properties
     testProperties_sed.properties

2) I read in the README.html in the java/testing directory that adding an entry in Sed.java
would help me in masking these. I guess in Sed.java I would do two things
    2.a) Add an entry for substitution of the pattern
    2.b) Add an entry for deletion of the pattern

Is there someone who has worked with the sed masking before? Can someone pls advice me on
the best way to proceed here?

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

        

Mime
View raw message