Bug #9221 Can't add a comment to a closed bug

• Submitted: 16 Mar 2005 13:51
• Modified: 28 May 2005 15:11
• Reporter: Sergei Kulakov (Candidate Quality Contributor)
• Status: Duplicate
• Category: MySQL Websites: bugs.mysql.com
• Severity: S3 (Non-critical)
• Version: --
• OS: --
• Assigned to: Assigned Account
• CPU Architecture: Any

[16 Mar 2005 13:51] Sergei Kulakov

Description:
I reported a bug http://bugs.mysql.com/bug.php?id=9201 .
In a day I received a reply stating that was not a bug and that the bug is closed. Now I want to add a comment because the report was misunderstood, but when I try to do it I get the same error message "You can't edit a bug that was closed" that I get if I go to the Edit bug page. 

How to repeat:
1. Go to the page http://bugs.mysql.com/bug.php?id=9201
2. Click "Edit Submission", you will receive the message "You can't edit a bug that has been marked closed. What you can do, is add a comment and if that is relevant, the MySQL Team will re-open the bug.". That's ok. 
3. Go to "Add Comment", for a reason you will get to the "Edit Submission" page but without the message. This is already strange. 
4. Try to add a fake comment and you will receive the error message aghain.

[22 Mar 2005 16:24] Sergei Kulakov

Can I have the following added to the bug 9201 as a comment in this case?
------------------------------------------------------------------------
I'm sorry, perhaps I didn't put much emphasis onto it, but the wrong column was Status which normally returns Suspended but becomes Pending when I insert the query into the table, not Price. It was not about using a column's default value in case a NULL value is inserted into it. The column Status belongs to the first table - Hotels - and returns "Suspended" for the 2nd row, not a NULL value. The first column - HotelId - belongs to the same table and is not NULL either (65). As I use Left Join all rows from the first table must be found and they are. Only the second column - Price - returns NULL in the 2nd row, and it is converted into 0 when I insert the query result into the table tmpHotData - this is absolutely alright. 
Another sign of  it is that the behavior changes back to normal if the column AreaId is removed from the querty/table, which shouldn't be the case if the behavior were expected. 
Note that MySql 4.1 only gives a warning about the Price column, not the Status column. 
I also checked this thing with MySql 4.1.9 and it produced correct results. 
------------------------------------------------------------------------

[28 May 2005 15:11] Indrek Siitan

This is a duplicate of #9349 and has been fixed.