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 Kathey Marsden <km...@sbcglobal.net> on 2005/09/15 20:38:47 UTC

Bug tracking for the 10.1.2 release

Hello All,

Time to gear up for the 10.1.2 release!   Target release date: *October 28*.

Take a look at the Jira generated release notes to see what's marked as
Fix Version 10.1.2.
http://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12310270&styleName=Text&projectId=10594&Create=Create

Of the issues listed,  there are 8  still  open (including a couple doc
bugs).
http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10594&fixfor=12310270

Issues:
  -  Dan and  Philip could you tell us the status of DERBY-467,
DERBY-406 and  DERBY-410?
      These have partial check ins in the 10.1.2 branch but are not
marked Fix Version 10.1.2.
   - What other things should we  fix for 10.1.2?

Please ...
  - Consider picking up a bug or two for the release. 
     (Check the "Derby open code bugs"  filter for a list of open bugs).
  - Mark bugs that you plan to fix for 10.1.2 as Fix Version 10.1.2 in Jira.
  -  Submit those patches early  to avoid the rush.  Fixes should be
*committed by  October 21*
     to provide a week for voting and testing.
  - Check the open issues for 10.1.2 and change the Fix Version if you
don't think your fix will
       make it for the release.

Thanks

Kathey

Re: Bug tracking for the 10.1.2 release

Posted by Philip Wilder <05...@acadiau.ca>.
Kathey Marsden wrote:

>Philip Wilder wrote:
>  
>
>>Hi Kathey,
>>
>>I'm afraid Derby-406 and Derby-410 have be stagnating. While the
>>original issue was resolved there still exists the issue of setting
>>the properties to null. You'll see that I have released these issues
>>as I have little time to devote to Derby development at present.
>>    
>>
>
>Thanks for the update Philip.
>
>I think it is important for the release notes to show what has been  
>fixed in 10.1.2.
>Would you mind reassigning yourself and marking these resolved and then
>opening a new issue for what is left to be done?   
>
>Thanks
>
>Kathey
>  
>

I took another look at the problems just to refresh my mind as to what 
the remaining concerns were and here is what I found. This is Dan's 
comment in regards to the patch submitted for these issues:

"I do not believe that this patch fully addresses these issues so they 
should not be closed, though it is good progress.
My concern is about the concept of defaults for DataSource properties, 
in these cases

406 - user - default of APP
409 - connectionAttributes - default of empty string
410 - serverName - default of localhost

All these properties are set to the default when the object is created, 
however if the values are set to null
(e.g. setConnecitonAttributes(null)) then should their values revert to 
the default or remain at null?
Existing data sources do not have any properties that have a default.

In the case that the property remains at null, then tests would be 
needed to ensure null is handled correctly,
at least for connectionAttributes I think a NullPointerException will 
occur."

A few tests yield the following results:

    Setting the username to null provides the following error message:
    org.apache.derby.client.am.SqlException: null userid not supported

    Setting the server name to null provides the following error message:
    org.apache.derby.client.am.DisconnectException: Required property
    "serverName" not set

    Setting connection attributes to null simply means that the
    connectionAttributes String is not processed at all. No
    NullPointerExceptions that I could find.


If we want to allow these values to be set to null these strike me as 
suitable error messages and no further work need be done. If we want 
them to revert to their default values that should also be fairly 
trivial to set up.

I guess the real issue here is just making the decision and it might as 
well be now rather then setting up a seperate jira issue to deal with it 
later.

Philip

Re: Bug tracking for the 10.1.2 release

Posted by Kathey Marsden <km...@sbcglobal.net>.
Philip Wilder wrote:

> Kathey Marsden wrote:
>
>> Issues:
>>  -  Dan and  Philip could you tell us the status of DERBY-467,
>> DERBY-406 and  DERBY-410?
>>
> Hi Kathey,
>
> I'm afraid Derby-406 and Derby-410 have be stagnating. While the
> original issue was resolved there still exists the issue of setting
> the properties to null. You'll see that I have released these issues
> as I have little time to devote to Derby development at present.

Thanks for the update Philip.

I think it is important for the release notes to show what has been  
fixed in 10.1.2.
Would you mind reassigning yourself and marking these resolved and then
opening a new issue for what is left to be done?   

Thanks

Kathey

Re: Bug tracking for the 10.1.2 release

Posted by Philip Wilder <05...@acadiau.ca>.
Kathey Marsden wrote:

>Issues:
>  -  Dan and  Philip could you tell us the status of DERBY-467,
>DERBY-406 and  DERBY-410?
>
Hi Kathey,

I'm afraid Derby-406 and Derby-410 have be stagnating. While the 
original issue was resolved there still exists the issue of setting the 
properties to null. You'll see that I have released these issues as I 
have little time to devote to Derby development at present.

Philip