Closed
Bug 303147
Opened 19 years ago
Closed 19 years ago
[PostgreSQL] Submitting a bug in the UNCONFIRMED state gives an error
Categories
(Bugzilla :: Database, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.20
People
(Reporter: emmanuel, Assigned: LpSolit)
Details
Attachments
(1 file)
|
1.38 KB,
patch
|
mkanat
:
review+
|
Details | Diff | Splinter Review |
When voting in activated and the UNCONFIRMED state is used, developers of a
product have a choice between the NEW and UNCONFIRMED states when submitting a bug.
Using PgSQL, submitting a bug in the UNCONFIRMED state gives:
DBD::Pg::st execute failed: ERREUR: Une valeur NULL dans la colonne
«everconfirmed» viole la contrainte NOT NULL
[for Statement "INSERT INTO bugs
(version,rep_platform,bug_severity,priority,op_sys,assigned_to,bug_status,bug_file_loc,short_desc,target_milestone,product_id,component_id,
reporter, delta_ts, estimated_time, remaining_time, deadline) VALUES
('other','PC','normal','P2','Linux','1','UNCONFIRMED','','totot','---','1','1',1,
'2005-08-02 23:28:43.600838+02', 0, 0, NULL)"] at Bugzilla/DB.pm line 81
Bugzilla::DB::SendSQL('INSERT INTO bugs
(version,rep_platform,bug_severity,priority,...') called at
/var/www/html/bugzilla-2.20/post_bug.cgi line 386| Assignee | ||
Comment 1•19 years ago
|
||
I confirm the bug. I tested on pg-tip with a user account which has no privs. This means that all users without canconfirm/editbugs privs cannot submit new bugs. mkanat, this makes sense to fix this bug for 2.20rc2 or we will have a plenty of dupes.
Severity: normal → critical
Flags: blocking2.20?
OS: Linux → All
Hardware: PC → All
Target Milestone: --- → Bugzilla 2.20
| Assignee | ||
Comment 2•19 years ago
|
||
everconfirmed should always be defined. Updating the schema to DEFAULT => '0' is not a good idea as some products do not use votes; and then the bug is confirmed by default.
Comment 3•19 years ago
|
||
Actually, Pg bugs are never blockers, since Pg support is "experimental" in 2.20. However, I'll certainly still take it for 2.20rc2. :-)
Flags: blocking2.20? → blocking2.20-
Comment 4•19 years ago
|
||
Comment on attachment 191417 [details] [diff] [review] patch, v1 OK, works, looks good to me. :-)
Attachment #191417 -
Flags: review?(mkanat) → review+
| Assignee | ||
Updated•19 years ago
|
Flags: approval?
Flags: approval2.20?
Updated•19 years ago
|
Flags: approval?
Flags: approval2.20?
Flags: approval2.20+
Flags: approval+
| Assignee | ||
Comment 5•19 years ago
|
||
tip: Checking in post_bug.cgi; /cvsroot/mozilla/webtools/bugzilla/post_bug.cgi,v <-- post_bug.cgi new revision: 1.120; previous revision: 1.119 done 2.20rc1: Checking in post_bug.cgi; /cvsroot/mozilla/webtools/bugzilla/post_bug.cgi,v <-- post_bug.cgi new revision: 1.118.2.1; previous revision: 1.118 done
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•