Blank resolution causing problems

[Ray Mike Troy Pello]

All,

I have had similar problems with the "" and "---" strings.
I have put the status "UNRESOLVED". This happens when you create a new bug.
Subsequently, the status should be unresolved when clearing the 
resolution and changed the default value on the resolution field to have 
"UNRESOLVED"
Also added the checksetup.pl checking so when you run checksetup it 
wouldn't change the default values on the tables.

Several tweakings are made also on query and report so the status would 
be shown.

I hope this can help with these problems.

Thx
Ray Pello

Christian Robottom Reis wrote:

>On Sun, Apr 10, 2005 at 07:20:43AM +0300, Vlad Dascalu wrote:
>  
>
>>Gervase Markham wrote:
>>
>>    
>>
>>>(Using "NULL" in the database instead of "" may make database purists
>>>      
>>>
>
>  
>
>>>happier, but doesn't solve this problem as far as I can see.)
>>>      
>>>
>>It would solve the issue of having (in the future :) ) custom 
>>resolutions and one named "---" or "[None]", and then having confused 
>>users all over the place. To begin with :)
>>    
>>
>
>Yeah, using strings to indicate cases with special semantics depresses
>me somewhat, because it's one more codepath that needs to be
>special-cased everywhere the name is created/changed..
>
>Take care,
>--
>Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3361
>2331
>-
>To view or change your list settings, click here:
><http://bugzilla.org/cgi-bin/mj_wwwusr?user=rpello@balicamp.com>
>
>  
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20050412/9294a6b6/attachment.html>