Open Bug 297791 Opened 19 years ago Updated 10 years ago

All instances of Bugzilla::Object should have ->create() and ->update() implemented


(Bugzilla :: Administration, task)

Not set




(Reporter: timello, Unassigned)


(Depends on 1 open bug)


(Keywords: meta, Whiteboard: [roadmap: 4.0])


(3 files, 1 obsolete file)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050405 Firefox/1.0 (Ubuntu package 1.0.2)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050405 Firefox/1.0 (Ubuntu package 1.0.2)

Step 2: Write/Validation Functions
We need methods and/or subroutines for validations and database persistence.
All related routines about inserts, updates, deletes and validations for those
routines have to be implemented at this bug.

Reproducible: Always

Steps to Reproduce:
Assignee: administration → timello
Ever confirmed: true
Depends on: 294160
Blocks: 293524
I think we should split validation and DB-persistence into separate bugs.
Target Milestone: --- → Bugzilla 2.22
Version: unspecified → 2.19.3
This routine belongs to
Attachment #186497 - Attachment is obsolete: true
Attachment #186497 - Attachment is obsolete: false
Assignee: timello → gabriel
Assignee: gabriel → batosti
Attached patch batosti_v1 (obsolete) — Splinter Review
an initial version.
Attachment #195411 - Flags: review?(LpSolit)
Attached patch batosti_v2Splinter Review
more things for the
Attachment #195411 - Attachment is obsolete: true
Attachment #195461 - Flags: review?(LpSolit)
Attachment #195411 - Flags: review?(LpSolit)
bug 299753 should be fixed first, and objects should be used instead of old
code. This bug should not be a simple copy and paste from editproducts.cgi into
Depends on: 299753
Comment on attachment 195461 [details] [diff] [review]

r- per my previous comment. And please remove the corresponding code from
editproducts.cgi (after the blocker is fixed).
Attachment #195461 - Flags: review?(LpSolit) → review-
No longer blocks: 293524
Depends on: 293524
Depends on: 313122
Depends on: 313123
Depends on: 313125
Depends on: 313129
Depends on: 313126
The trunk is now frozen to prepare Bugzilla 2.22. Enhancement bugs are retargetted to 2.24.
Target Milestone: Bugzilla 2.22 → Bugzilla 2.24
We are in "soft freeze" mode to prepare 3.0 RC1.
Target Milestone: Bugzilla 3.0 → Bugzilla 3.2
Whiteboard: [roadmap: 3.2]
Keywords: meta
Summary: Step 2 (RW): implement validations and database persistence functions for,, and → All instances of Bugzilla::Object should have ->create() and ->update() implemented
Depends on: bz-object
Bugzilla 3.2 is now frozen. Only enhancements blocking 3.2 or specifically approved for 3.2 may be checked in to the 3.2 branch. If you would like to nominate your enhancement for Bugzilla 3.2, set the "blocking3.2" flag to "?", and either the target milestone will be changed back, or the blocking3.2 flag will be granted, if we will accept this enhancement for Bugzilla 3.2.
Target Milestone: Bugzilla 3.2 → Bugzilla 4.0
Whiteboard: [roadmap: 3.2] → [roadmap: 4.0]
Depends on: 454251
Assignee: batosti → administration
Depends on: 415541
We are going to branch for Bugzilla 4.4 next week and this bug is too invasive or too risky to be accepted for 4.4 at this point. The target milestone is set to 5.0 which is our next major release.

I ask the assignee to reassign the bug to the default assignee if you don't plan to work on this bug in the near future, to make it clearer which bugs should be fixed by someone else on time for 5.0.
Target Milestone: Bugzilla 4.4 → Bugzilla 5.0
Target Milestone: Bugzilla 5.0 → ---
You need to log in before you can comment on or make changes to this bug.