Skip to content

Commit 246bb47

Browse files
authored
Edit. (#220)
1 parent cb8e025 commit 246bb47

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

docs/source/examples/example_dates.rst

+5-4
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
Example: Dates
22
==============
33

4-
This example concerns itself with expressing ``Constraint``s against data revolving
5-
around dates. While date ``Constraint``s between tables exist, we will only illustrate
6-
``Constraint``s on a single table and reference values here. As a consequence, we will
4+
This example concerns itself with expressing ``Constraint``\s against data revolving
5+
around dates. While date ``Constraint``\s between tables exist, we will only illustrate
6+
``Constraint``\s on a single table and reference values here. As a consequence, we will
77
only use ``WithinRequirement``, as opposed to ``BetweenRequirement``.
88

99
Concretely, we will assume a table containing prices for a given product of id 1.
@@ -156,7 +156,8 @@ Assuming that such a table exists in database, we can write a specification agai
156156
Pleas note that the ``DateNoOverlap`` and ``DateNoGap`` constraints also exist
157157
in a slightly different form: ``DateNoOverlap2d`` and ``DateNoGap2d``.
158158
As the names suggest, these can operate in 'two date dimensions'.
159-
It could for instance be, that a table has four date columns, representing two
159+
160+
For example, let's assume a table with four date columns, representing two
160161
ranges in distinct dimensions, respectively:
161162

162163
* ``date_from``: Date from when a price is valid

0 commit comments

Comments
 (0)