mirror of
https://github.com/go-vikunja/vikunja.git
synced 2026-07-20 21:14:30 -05:00
Add a second reminder to task 2 (in 2019, outside the test window) and create task #47 with two reminders that straddle the test window (2018-08-01 and 2019-03-01) but neither falls inside it. This exposes the multi-row matching bug where separate EXISTS subqueries can match different rows in the same sub-table.
38 lines
1.0 KiB
YAML
38 lines
1.0 KiB
YAML
- id: 1
|
|
task_id: 27
|
|
reminder: 2018-12-01 01:12:04
|
|
created: 2018-12-01 01:12:04
|
|
- id: 2
|
|
task_id: 27
|
|
reminder: 2018-12-01 01:13:44
|
|
created: 2018-12-01 01:12:04
|
|
relative_to: 'start_date'
|
|
relative_period: -3600
|
|
- id: 3
|
|
task_id: 2
|
|
reminder: 2018-12-01 01:13:44
|
|
created: 2018-12-01 01:12:04
|
|
- id: 4
|
|
task_id: 40
|
|
reminder: 2023-03-04 15:00:00
|
|
created: 2018-12-01 01:12:04
|
|
# Task 2 already has one reminder at 2018-12-01 01:13:44 (id 3).
|
|
# Add a second reminder for task 2 that is far outside the range used by
|
|
# the "filtered reminder dates" test (2018-10-01 to 2018-12-10).
|
|
# This second reminder is in 2019, well after the upper bound.
|
|
- id: 5
|
|
task_id: 2
|
|
reminder: 2019-06-01 12:00:00
|
|
created: 2018-12-01 01:12:04
|
|
# Task 47: two reminders, neither inside the (2018-10-01, 2018-12-10) window
|
|
# Reminder before the window:
|
|
- id: 6
|
|
task_id: 47
|
|
reminder: 2018-08-01 12:00:00
|
|
created: 2018-12-01 01:12:04
|
|
# Reminder after the window:
|
|
- id: 7
|
|
task_id: 47
|
|
reminder: 2019-03-01 12:00:00
|
|
created: 2018-12-01 01:12:04
|