Closed
Bug 339670
Opened 18 years ago
Closed 18 years ago
SQL query for non-recurrent events is not correct
Categories
(Calendar :: Internal Components, defect)
Calendar
Internal Components
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: thomas.benisch, Assigned: thomas.benisch)
Details
(Keywords: dataloss)
Attachments
(1 file)
2.20 KB,
patch
|
dmosedale
:
first-review+
|
Details | Diff | Splinter Review |
In the storage calendar the SQL query for non-recurrent events is not correct for the case start_offset != end_offset.
Assignee | ||
Comment 2•18 years ago
|
||
start_offset always refers to range_start, end_offset always refers to range_end
Attachment #224187 -
Flags: first-review?(dmose)
Updated•18 years ago
|
Comment 3•18 years ago
|
||
Comment on attachment 224187 [details] [diff] [review] patch v1 Looks good; thanks for the patch. I'm taking the liberty of also correcting the pseudo-code in the (already existing) comment, as it has a thinko.
Attachment #224187 -
Flags: first-review?(dmose) → first-review+
Comment 4•18 years ago
|
||
Fix checked in using cross-commit on both branch and trunk. I also added your name and email address to the license boilerplate changes at the top of the file.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•