diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-11-04 03:09:12 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-11-04 03:09:12 +0300 |
| commit | 8d94fb4ae136386963c5353f72b227b9c27af4d7 (patch) | |
| tree | 96ac46df8328893611554fca5533e520c78fe27a /doc/development/value_stream_analytics.md | |
| parent | 037bda35bf0edc43a591348d4fda01f436389c60 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/value_stream_analytics.md')
| -rw-r--r-- | doc/development/value_stream_analytics.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/value_stream_analytics.md b/doc/development/value_stream_analytics.md index 4005718bfda..90d7597d46f 100644 --- a/doc/development/value_stream_analytics.md +++ b/doc/development/value_stream_analytics.md @@ -59,8 +59,8 @@ def timestamp_projection end ``` -NOTE: **Note:** -More complex expressions are also possible (e.g. using `COALESCE`). Look at the existing event classes for examples. +More complex expressions are also possible (for example, using `COALESCE`). +Review the existing event classes for examples. In some cases, defining the `timestamp_projection` method is not enough. The calculation query should know which table contains the timestamp expression. Each `Event` class is responsible for making modifications to the calculation query to make the `timestamp_projection` work. This usually means joining an additional table. |