You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Rajesh Kartha <ka...@gmail.com> on 2006/11/20 07:59:17 UTC
Issues that are fixed in trunk and needs to be reviewed for porting
to 10.2 branch
Hello,
I am yet to find a simple way in JIRA to review the list of issues
which are fixed in trunk and could be ported to
branches.
Anyways, I wrote a simple utility to dump all the DERBY related JIRA
data into a database and enable me to
run SQL queries.
(If the community thinks such a utility might be useful for Derby, I am
more than happy to contribute that).
Based on that, please find attached the current list of JIRA issues that
are candidates for porting to the
10.2 branch. My query was:
"select jira_issue, component,fixversions, title from jira_issues where
Resolution='Fixed' and affectedversions!='10.3.0.0'
and fixversions='10.3.0.0' and type='Bug' and component not in
('Test','Regression Test Failure') order by component;"
I have excluded the Test component. My initial review of the full list
shows that the following issues needs to be
considered for porting to the 10.2 branch:
============================================================
DERBY-1732 |Store |10.3.0.0 |[DERBY-1732] The
language and store systems treat a JVM error such
as
OutOfMemoryError differently leading to the raw store pro&
DERBY-1304 |SQL |10.3.0.0 |[DERBY-1304] DROP view
does not always completely remove
view
DERBY-1589 |SQL |10.3.0.0 |[DERBY-1589] CREATE
TABLE throws NullPointerException in
Derby SQL Standard Authorization after DROPs and REVOKES
DERBY-1716 |SQL |10.3.0.0 |[DERBY-1716] Revoking
select privilege from a user times out when
that
user still have a cursor open.
DERBY-2008 |SQL |10.3.0.0 |[DERBY-2008]
NullPointerException with LTRIM, RTRIM
and
2-argument SUBSTR() call in GROUP BY clause.
DERBY-2014 |SQL |10.3.0.0 |[DERBY-2014]
NullPointerException with NULLIF in
GROUP
BY clause
Other possible candidates are: DERBY-1811, DERBY-1693. I have not
included any Documentation issues in this yet.
Any thoughts/comments please do send a mail to the list.
Also, once we have an agreement on the list of portable issues can the
committers look into doing the needful
merges to the branch
Regards,
Rajesh
Re: Issues that are fixed in trunk and needs to be reviewed for
porting to 10.2 branch
Posted by Rick Hillegas <Ri...@Sun.COM>.
At this point, the high value issues identified by Rajesh have been
ported to the 10.2 branch: DERBY-1732, DERBY-1304, DERBY-1589,
DERBY-1716, DERBY-2008, DERBY-2014, DERBY-1811, DERBY-1693.
Regards,
-Rick
Rajesh Kartha wrote:
> Hello,
>
> I am yet to find a simple way in JIRA to review the list of issues
> which are fixed in trunk and could be ported to
> branches.
>
> Anyways, I wrote a simple utility to dump all the DERBY related JIRA
> data into a database and enable me to
> run SQL queries.
> (If the community thinks such a utility might be useful for Derby, I
> am more than happy to contribute that).
>
> Based on that, please find attached the current list of JIRA issues
> that are candidates for porting to the
> 10.2 branch. My query was:
>
> "select jira_issue, component,fixversions, title from jira_issues
> where Resolution='Fixed' and affectedversions!='10.3.0.0'
> and fixversions='10.3.0.0' and type='Bug' and component not in
> ('Test','Regression Test Failure') order by component;"
>
> I have excluded the Test component. My initial review of the full list
> shows that the following issues needs to be
> considered for porting to the 10.2 branch:
>
> ============================================================
> DERBY-1732 |Store |10.3.0.0 |[DERBY-1732] The
> language and store systems treat a JVM error such
> as
> OutOfMemoryError differently leading to the raw store pro&
> DERBY-1304 |SQL |10.3.0.0 |[DERBY-1304] DROP view
> does not always completely remove
> view
> DERBY-1589 |SQL |10.3.0.0 |[DERBY-1589] CREATE
> TABLE throws NullPointerException in
>
> Derby SQL Standard Authorization after DROPs and REVOKES
> DERBY-1716 |SQL |10.3.0.0 |[DERBY-1716] Revoking
> select privilege from a user times out when
>
> that user still have a cursor open.
> DERBY-2008 |SQL |10.3.0.0 |[DERBY-2008]
> NullPointerException with LTRIM, RTRIM
> and
> 2-argument SUBSTR() call in GROUP BY clause.
> DERBY-2014 |SQL |10.3.0.0 |[DERBY-2014]
> NullPointerException with NULLIF in
> GROUP
> BY clause
> Other possible candidates are: DERBY-1811, DERBY-1693. I have not
> included any Documentation issues in this yet.
>
> Any thoughts/comments please do send a mail to the list.
> Also, once we have an agreement on the list of portable issues can the
> committers look into doing the needful
> merges to the branch
>
> Regards,
> Rajesh
>
>
>
>
>
> ------------------------------------------------------------------------
>
> --Query:
> --select jira_issue, component,fixversions, title from jira_issues where Resolution='Fixed' and affectedversions!='10.3.0.0' and fixversions='10.3.0.0' and type='Bug' and component not in ('Test','Regression Test Failure') order by component;
> --
> --
> JIRA_ISSUE |COMPONENT |FIXVERSIONS |TITLE
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> DERBY-1741 | |10.3.0.0 |[DERBY-1741] Remove the references for cloudscape and cloudcape
> DERBY-1843 | |10.3.0.0 |[DERBY-1843] new dblook.bat does not pass on arguments
> DERBY-1975 | |10.3.0.0 |[DERBY-1975] SQLAuthorizationPropTest cannot be run twice against the same database.
> DERBY-1588 |Demos/Scripts |10.3.0.0 |[DERBY-1588] Link "Getting Started...." and "Apache Derby Server ...." in demo.html needs to be linked to actual documents inst&
> DERBY-1753 |Documentation |10.3.0.0 |[DERBY-1753] Doc for SYSCS_INPLACE_COMPRESS_TABLE has incorrect procedure name in the java examples.
> DERBY-1795 |Documentation |10.3.0.0 |[DERBY-1795] Graphics not copied over for PDF and HTML-single manuals
> DERBY-1805 |Documentation |10.3.0.0 |[DERBY-1805] Links to element ids inside a topic are broken in PDFs and HTML Books
> DERBY-1822 |Documentation |10.3.0.0 |[DERBY-1822] LOCK TABLE example and description in reference manual should get replaced by a 'real' example
> DERBY-1918 |Documentation |10.3.0.0 |[DERBY-1918] INCREMENT of IDENTITY column described as allowing a value of zero in reference manual
> DERBY-2001 |Documentation |10.3.0.0 |[DERBY-2001] Add DITA templates for the 3 topic types into the trunk
> DERBY-2088 |Documentation |10.3.0.0 |[DERBY-2088] Update the documentation templates. Add comment about changing the reference ID
> DERBY-1494 |JDBC |10.3.0.0 |[DERBY-1494] PreparedStatement.setNull(int, int) checks type compatibility on embedded, but not on the client
> DERBY-1501 |JDBC |10.3.0.0 |[DERBY-1501] PreparedStatement#setNull(int parameterIndex, int sqlType) throws SQL Exception if given sqlType is LONGVARBINARY &
> DERBY-1811 |JDBC |10.3.0.0 |[DERBY-1811] Embedded ResultSet.getTimestamp on a TIME column returns a java.sql.Timestamp with a date portion that can be inco&
> DERBY-147 |SQL |10.3.0.0 |[DERBY-147] ERROR 42X79 not consistant ? - same column name specified twice
> DERBY-183 |SQL |10.3.0.0 |[DERBY-183] Parameter names required in CREATE FUNCTION
> DERBY-630 |SQL |10.3.0.0 |[DERBY-630] create trigger fails with null pointer exception
> DERBY-729 |SQL |10.3.0.0 |[DERBY-729] Scalar time and date functions return 0 instead NULL when argument is NULL
> DERBY-1304 |SQL |10.3.0.0 |[DERBY-1304] DROP view does not always completely remove view
> DERBY-1589 |SQL |10.3.0.0 |[DERBY-1589] CREATE TABLE throws NullPointerException in Derby SQL Standard Authorization after DROPs and REVOKES
> DERBY-1693 |SQL |10.3.0.0 |[DERBY-1693] Out of Memory Error with derby.language.logStatementText=true
> DERBY-1716 |SQL |10.3.0.0 |[DERBY-1716] Revoking select privilege from a user times out when that user still have a cursor open.
> DERBY-1836 |SQL |10.3.0.0 |[DERBY-1836] Message XJ215 should be updated to reflect that Clob/Blob are referring to method calls.
> DERBY-2008 |SQL |10.3.0.0 |[DERBY-2008] NullPointerException with LTRIM, RTRIM and 2-argument SUBSTR() call in GROUP BY clause.
> DERBY-2014 |SQL |10.3.0.0 |[DERBY-2014] NullPointerException with NULLIF in GROUP BY clause
> DERBY-2018 |SQL |10.3.0.0 |[DERBY-2018] NullPointerException in CREATE VIEW ... VALUES NULL;
> DERBY-1732 |Store |10.3.0.0 |[DERBY-1732] The language and store systems treat a JVM error such as OutOfMemoryError differently leading to the raw store pro&
> DERBY-1783 |Store |10.3.0.0 |[DERBY-1783] Logical error in code for determining mode for opening of log files
> DERBY-415 |Tools |10.3.0.0 |[DERBY-415] sysinfo with -cp client option should not print error saying DB2 jar file and driver class are missing
>
> 28 rows selected
>
>
Re: Issues that are fixed in trunk and needs to be reviewed for
porting to 10.2 branch
Posted by Vemund Ostgaard <Ve...@Sun.COM>.
Rajesh Kartha wrote:
> Hello,
>
> I am yet to find a simple way in JIRA to review the list of issues
> which are fixed in trunk and could be ported to
> branches.
>
> Anyways, I wrote a simple utility to dump all the DERBY related JIRA
> data into a database and enable me to
> run SQL queries.
> (If the community thinks such a utility might be useful for Derby, I
> am more than happy to contribute that).
+1
I think that could be useful for Derby if we want to implement some
metrics based on the information in Jira for instance.
Vemund
Re: Issues that are fixed in trunk and needs to be reviewed for
porting to 10.2 branch
Posted by Rick Hillegas <Ri...@Sun.COM>.
Rajesh Kartha wrote:
> Thanks Vemund, Rick for your replies.
> I will open a JIRA issue and contribute the utility.
>
>>
>>
>> Just a heads-up that I'm still planning to cat-herd a 10.2.2 release
>> in early December. I think we have two solid weeks to port fixes to
>> 10.2 before I cut a release candidate.
>>
>> Regards,
>> -Rick
>>
> I was wondering wouldn't it be useful if the fixes get ported to 10.2
> branch in smaller batches but at
> regular intervals rather than huge merges towards the end.
> It will be simpler that way and we can avoid any last minute surprises.
>
> Regards,
> Rajesh
>
>
Yes, please. I would be happy to see people port their fixes to the next
release vehicle soon after checking into the mainline. I agree that this
results in fewer surprises. For the record, I'm not planning to
mega-merge from the trunk into the 10.2.2 release. This porting effort
is a scratch-your-own-itch opportunity.
Regards,
-Rick
>
>
Re: Issues that are fixed in trunk and needs to be reviewed for
porting to 10.2 branch
Posted by Rajesh Kartha <ka...@gmail.com>.
Thanks Vemund, Rick for your replies.
I will open a JIRA issue and contribute the utility.
>
>
> Just a heads-up that I'm still planning to cat-herd a 10.2.2 release
> in early December. I think we have two solid weeks to port fixes to
> 10.2 before I cut a release candidate.
>
> Regards,
> -Rick
>
I was wondering wouldn't it be useful if the fixes get ported to 10.2
branch in smaller batches but at
regular intervals rather than huge merges towards the end.
It will be simpler that way and we can avoid any last minute surprises.
Regards,
Rajesh
Re: Issues that are fixed in trunk and needs to be reviewed for
porting to 10.2 branch
Posted by Rick Hillegas <Ri...@Sun.COM>.
Thanks Rajesh,
Just a heads-up that I'm still planning to cat-herd a 10.2.2 release in
early December. I think we have two solid weeks to port fixes to 10.2
before I cut a release candidate.
Regards,
-Rick
Rajesh Kartha wrote:
> Hello,
>
> I am yet to find a simple way in JIRA to review the list of issues
> which are fixed in trunk and could be ported to
> branches.
>
> Anyways, I wrote a simple utility to dump all the DERBY related JIRA
> data into a database and enable me to
> run SQL queries.
> (If the community thinks such a utility might be useful for Derby, I
> am more than happy to contribute that).
>
> Based on that, please find attached the current list of JIRA issues
> that are candidates for porting to the
> 10.2 branch. My query was:
>
> "select jira_issue, component,fixversions, title from jira_issues
> where Resolution='Fixed' and affectedversions!='10.3.0.0'
> and fixversions='10.3.0.0' and type='Bug' and component not in
> ('Test','Regression Test Failure') order by component;"
>
> I have excluded the Test component. My initial review of the full list
> shows that the following issues needs to be
> considered for porting to the 10.2 branch:
>
> ============================================================
> DERBY-1732 |Store |10.3.0.0 |[DERBY-1732] The
> language and store systems treat a JVM error such
> as
> OutOfMemoryError differently leading to the raw store pro&
> DERBY-1304 |SQL |10.3.0.0 |[DERBY-1304] DROP view
> does not always completely remove
> view
> DERBY-1589 |SQL |10.3.0.0 |[DERBY-1589] CREATE
> TABLE throws NullPointerException in
>
> Derby SQL Standard Authorization after DROPs and REVOKES
> DERBY-1716 |SQL |10.3.0.0 |[DERBY-1716] Revoking
> select privilege from a user times out when
>
> that user still have a cursor open.
> DERBY-2008 |SQL |10.3.0.0 |[DERBY-2008]
> NullPointerException with LTRIM, RTRIM
> and
> 2-argument SUBSTR() call in GROUP BY clause.
> DERBY-2014 |SQL |10.3.0.0 |[DERBY-2014]
> NullPointerException with NULLIF in
> GROUP
> BY clause
> Other possible candidates are: DERBY-1811, DERBY-1693. I have not
> included any Documentation issues in this yet.
>
> Any thoughts/comments please do send a mail to the list.
> Also, once we have an agreement on the list of portable issues can the
> committers look into doing the needful
> merges to the branch
>
> Regards,
> Rajesh
>
>
>
>
>
> ------------------------------------------------------------------------
>
> --Query:
> --select jira_issue, component,fixversions, title from jira_issues where Resolution='Fixed' and affectedversions!='10.3.0.0' and fixversions='10.3.0.0' and type='Bug' and component not in ('Test','Regression Test Failure') order by component;
> --
> --
> JIRA_ISSUE |COMPONENT |FIXVERSIONS |TITLE
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> DERBY-1741 | |10.3.0.0 |[DERBY-1741] Remove the references for cloudscape and cloudcape
> DERBY-1843 | |10.3.0.0 |[DERBY-1843] new dblook.bat does not pass on arguments
> DERBY-1975 | |10.3.0.0 |[DERBY-1975] SQLAuthorizationPropTest cannot be run twice against the same database.
> DERBY-1588 |Demos/Scripts |10.3.0.0 |[DERBY-1588] Link "Getting Started...." and "Apache Derby Server ...." in demo.html needs to be linked to actual documents inst&
> DERBY-1753 |Documentation |10.3.0.0 |[DERBY-1753] Doc for SYSCS_INPLACE_COMPRESS_TABLE has incorrect procedure name in the java examples.
> DERBY-1795 |Documentation |10.3.0.0 |[DERBY-1795] Graphics not copied over for PDF and HTML-single manuals
> DERBY-1805 |Documentation |10.3.0.0 |[DERBY-1805] Links to element ids inside a topic are broken in PDFs and HTML Books
> DERBY-1822 |Documentation |10.3.0.0 |[DERBY-1822] LOCK TABLE example and description in reference manual should get replaced by a 'real' example
> DERBY-1918 |Documentation |10.3.0.0 |[DERBY-1918] INCREMENT of IDENTITY column described as allowing a value of zero in reference manual
> DERBY-2001 |Documentation |10.3.0.0 |[DERBY-2001] Add DITA templates for the 3 topic types into the trunk
> DERBY-2088 |Documentation |10.3.0.0 |[DERBY-2088] Update the documentation templates. Add comment about changing the reference ID
> DERBY-1494 |JDBC |10.3.0.0 |[DERBY-1494] PreparedStatement.setNull(int, int) checks type compatibility on embedded, but not on the client
> DERBY-1501 |JDBC |10.3.0.0 |[DERBY-1501] PreparedStatement#setNull(int parameterIndex, int sqlType) throws SQL Exception if given sqlType is LONGVARBINARY &
> DERBY-1811 |JDBC |10.3.0.0 |[DERBY-1811] Embedded ResultSet.getTimestamp on a TIME column returns a java.sql.Timestamp with a date portion that can be inco&
> DERBY-147 |SQL |10.3.0.0 |[DERBY-147] ERROR 42X79 not consistant ? - same column name specified twice
> DERBY-183 |SQL |10.3.0.0 |[DERBY-183] Parameter names required in CREATE FUNCTION
> DERBY-630 |SQL |10.3.0.0 |[DERBY-630] create trigger fails with null pointer exception
> DERBY-729 |SQL |10.3.0.0 |[DERBY-729] Scalar time and date functions return 0 instead NULL when argument is NULL
> DERBY-1304 |SQL |10.3.0.0 |[DERBY-1304] DROP view does not always completely remove view
> DERBY-1589 |SQL |10.3.0.0 |[DERBY-1589] CREATE TABLE throws NullPointerException in Derby SQL Standard Authorization after DROPs and REVOKES
> DERBY-1693 |SQL |10.3.0.0 |[DERBY-1693] Out of Memory Error with derby.language.logStatementText=true
> DERBY-1716 |SQL |10.3.0.0 |[DERBY-1716] Revoking select privilege from a user times out when that user still have a cursor open.
> DERBY-1836 |SQL |10.3.0.0 |[DERBY-1836] Message XJ215 should be updated to reflect that Clob/Blob are referring to method calls.
> DERBY-2008 |SQL |10.3.0.0 |[DERBY-2008] NullPointerException with LTRIM, RTRIM and 2-argument SUBSTR() call in GROUP BY clause.
> DERBY-2014 |SQL |10.3.0.0 |[DERBY-2014] NullPointerException with NULLIF in GROUP BY clause
> DERBY-2018 |SQL |10.3.0.0 |[DERBY-2018] NullPointerException in CREATE VIEW ... VALUES NULL;
> DERBY-1732 |Store |10.3.0.0 |[DERBY-1732] The language and store systems treat a JVM error such as OutOfMemoryError differently leading to the raw store pro&
> DERBY-1783 |Store |10.3.0.0 |[DERBY-1783] Logical error in code for determining mode for opening of log files
> DERBY-415 |Tools |10.3.0.0 |[DERBY-415] sysinfo with -cp client option should not print error saying DB2 jar file and driver class are missing
>
> 28 rows selected
>
>