Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Date: Tue, 05 Feb 2008 15:09:50 -0500
From: Kim Haase <Camilla.Haase@Sun.COM>
Subject: Re: Bug fixes in trunk that are not in 10.3 branch
In-reply-to: <47A792F1.9020803@sbcglobal.net>
Sender: Camilla.Haase@Sun.COM
To: derby-dev@db.apache.org
Reply-to: Camilla.Haase@Sun.COM
Message-id: <47A8C28E.3030905@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <47A75BD0.6040009@sbcglobal.net> <47A792F1.9020803@sbcglobal.net>
User-Agent: Thunderbird 2.0.0.6 (X11/20070802)

I notice that at least for doc bugs, there have been some cases that 
this report hasn't caught. Three bugs that I know of that were fixed for 
10.4 have empty version fields, and two of these have empty fixversion 
fields too:

DERBY-2240 (no version)
DERBY-3072, DERBY-3297 (no version or fixversion)

Two of these are closed, one is resolved. Would it make sense to fill in 
these fields? 3072 was fixed by Rick Hillegas, the other two by me.

There may be other such bugs; I don't know.

Thanks,
Kim

Kathey Marsden wrote:
> Myrna asked me how I generated this report.
> 1) I patched the demo to include a few extra columns.
> Index: java/demo/vtis/java/org/apache/derbyDemo/vtis/example/VTIs.java
> 
> ===================================================================
> 
> --- java/demo/vtis/java/org/apache/derbyDemo/vtis/example/VTIs.java    
> (revision 618330)
> 
> +++ java/demo/vtis/java/org/apache/derbyDemo/vtis/example/VTIs.java    
> (working copy)
> 
> @@ -94,8 +94,8 @@
> 
>     @XMLRow
>         (
>          rowTag = "item",
> -         childTags = { "key", "type", "priority", "status", 
> "component", "title" },
> -         childTypes = { "varchar(12)", "varchar(10)", "varchar(10)", 
> "varchar(10)", "varchar(50)", "varchar(200)" },
> +         childTags = { "key", "type", "assignee", "priority", "status", 
> "component", "version","fixVersion", "title","resolution" },
> +         childTypes = { "varchar(12)", "varchar(10)", "varchar(50)", 
> "varchar(10)", "varchar(10)", "varchar(50)", "varchar(150)", 
> "varchar(150)", "varchar(200)","varchar(20)" },
>          vtiClassName = "org.apache.derbyDemo.vtis.core.XmlVTI"
>          )
>     public  static  ResultSet   apacheVanillaJiraReport( String 
> xmlResource ) throws SQLException
> 
> I had to build the demo with javac -g -d $WS/classes. It did not seem to 
> build automatically as part of the build. I don't know if that is a 
> problem.
> 
> 2)  I ran the part of the demoFileVtis.sql file related to the JiraVTI
> 
> connect 'jdbc:derby:vtitest;create=true';
> 
> ---------------------------------------------------------------------------------------- 
> 
> -- 
> -- Drop and recreate the database procedures and tables needed
> -- by this demonstration script.
> -- 
> ---------------------------------------------------------------------------------------- 
> 
> 
> -- 
> -- Drop procedures and tables
> -- 
> drop procedure registerXMLRowVTIs;
> 
> -- 
> -- Drop miscellaneous table functions
> -- 
> drop function svnLogReader;
> drop function propertyFileVTI;
> 
> 
> -- 
> -- Recreate procedures
> -- 
> create procedure registerXMLRowVTIs( className varchar( 32672 ) )
> language java
> parameter style java
> modifies sql data
> external name 'org.apache.derbyDemo.vtis.core.XmlVTI.registerXMLRowVTIs'
> ;
> 
> ---------------------------------------------------------------------------------------- 
> 
> -- 
> -- Declare the table functions.
> -- 
> ---------------------------------------------------------------------------------------- 
> 
> 
> -- 
> -- Register the table functions in the VTIs class
> -- 
> call registerXMLRowVTIs( 'org.apache.derbyDemo.vtis.example.VTIs' );
> 
> -- 
> 
> 
> 3)  I ran the report.
> 
> select s."key", s."title", s."assignee"
> from table( "apacheVanillaJiraReport"( 
> 'file:///kmarsden/projects/tablefunction/all_JIRA_ISSUES.xml' ) ) s  
> where  "type" = 'Bug' AND "version" LIKE '%10.3%' AND "fixVersion" LIKE 
> '%10.4%'  AND NOT "fixVersion" LIKE '%10.3%'  AND "resolution" = 'Fixed';
> 
> 
> The version and the fixversion values are kind of weird with all the 
> versions smashed together, but the worked ok for my purposes.  I don't 
> know whether it would be appropriate to add them to the demo though in 
> that format.
> 
> Kathey
>