Closed
Bug 250591
Opened 21 years ago
Closed 21 years ago
Conversion of boolean conditions in SQL statements for better db independence (take 2)
Categories
(Bugzilla :: Bugzilla-General, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.20
People
(Reporter: dkl, Assigned: dkl)
References
Details
Attachments
(1 file)
790 bytes,
patch
|
goobix
:
review+
|
Details | Diff | Splinter Review |
One more spot was discovered by Tomas Kopal where a boolean condition needs to
be sanitized for better db independence. Patch forthcoming.
![]() |
||
Updated•21 years ago
|
OS: Linux → All
Hardware: PC → All
Assignee | ||
Comment 1•21 years ago
|
||
Assignee: justdave → dkl
Status: NEW → ASSIGNED
![]() |
||
Updated•21 years ago
|
Flags: approval2.18?
![]() |
||
Updated•21 years ago
|
Attachment #152701 -
Flags: review?(bugreport)
Assignee | ||
Comment 4•21 years ago
|
||
Ack, you're right. I meant review? but got the two mixed up, and then to top it
off hit the + instead of ?.
/me heads out for more coffee ;)
![]() |
||
Updated•21 years ago
|
Attachment #152701 -
Flags: review?(bugreport) → review+
![]() |
||
Updated•21 years ago
|
Flags: approval?
Flags: approval2.18?
![]() |
||
Comment 5•21 years ago
|
||
dkl: I'm assuming that there are a whole bunch of pgsql changes that will need
to go in that won't be on 2.18. Wouldn't it be better to target this for (very
early) 2.19??
Assignee | ||
Comment 6•21 years ago
|
||
I would think this one would be ok to get into 2.18 since it is not PgSQL
specific really. Plus this is part of my trying to break the huge PgSQL patch
down into smaller generic pieces for easier review. But I am up for whatever
others think.
Comment 7•21 years ago
|
||
ehhh... I don't want to mess with this this close to branch point. Let's check
it in on the trunk after we branch (that's happening later tonight).
2.18 isn't going to have multi-DB support anyway, so there's no reason it has to
be there.
Flags: approval2.18? → approval2.18-
Target Milestone: --- → Bugzilla 2.20
![]() |
||
Comment 8•21 years ago
|
||
*** Bug 250832 has been marked as a duplicate of this bug. ***
Updated•21 years ago
|
Flags: approval? → approval+
Assignee | ||
Comment 9•21 years ago
|
||
Just as a refresher, the approval that justdave granted means it is ok to check
this in against HEAD since 2.18 is not on it's own branch?
Tnanks
Updated•21 years ago
|
Blocks: bz-postgres
Comment 10•21 years ago
|
||
What is this one still waiting for? ;-)
![]() |
||
Comment 11•21 years ago
|
||
David: it's ok for you to check this in on the tip (on the HEAD).
You don't need to worry about branches (2_16, 2_18 etc).
Assignee | ||
Comment 12•21 years ago
|
||
Thanks, will get it in.
Comment 13•21 years ago
|
||
Another month gone, another whine :-). What is this waiting for now? :-)
![]() |
||
Comment 14•21 years ago
|
||
Checking in request.cgi;
/cvsroot/mozilla/webtools/bugzilla/request.cgi,v <-- request.cgi
new revision: 1.15; previous revision: 1.14
done
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•