|
8 | 8 | `neo4j.work`. They should've been imported from `neo4j` all along. |
9 | 9 | - Experimental pipelines feature has been removed. |
10 | 10 | - Experimental async driver has been added. |
| 11 | +- `neo4j.time` module: |
| 12 | + - `Duration` |
| 13 | + - The constructor does not accept `subseconds` anymore. |
| 14 | + Use `milliseconds`, `microseconds`, or `nanoseconds` instead. |
| 15 | + - The property `subseconds` has been removed. |
| 16 | + Use `nanoseconds` instead. |
| 17 | + - The property `hours_minutes_seconds` has been removed. |
| 18 | + Use `hours_minutes_seconds_nanoseconds` instead. |
| 19 | + - For all math operations holds: they are element-wise on |
| 20 | + (`months`, `days`, `nanoseconds`). |
| 21 | + This affects (i.e., changes) the working of `//`, `%`, `/`, and `*`. |
| 22 | + - Years are equal to 12 months. |
| 23 | + - Weeks are equal to 7 days. |
| 24 | + - `seconds`, `milliseconds`, `microseconds`, and `nanoseconds` are |
| 25 | + implicitly converted to `nanoseconds` or `seconds` as fit. |
| 26 | + - Multiplication and division allow for floats but will always result in |
| 27 | + integer values (round to nearest even). |
| 28 | + - `Time` |
| 29 | + - The constructor does not accept `float`s for `second` anymore. |
| 30 | + Use `nanosecond` instead. |
| 31 | + - Ticks are now nanoseconds since midnight (`int`). |
| 32 | + - The property `ticks_ns` has been renamed to `ticks`. |
| 33 | + The old `ticks` is no longer supported. |
| 34 | + - The property`from_ticks_ns` has been renamed to `from_ticks`. |
| 35 | + The old `from_ticks` is no longer supported. |
| 36 | + - The property `second` returns an `int` instead of a `float`. |
| 37 | + Use `nanosecond` to get the sub-second information. |
| 38 | + - The property `hour_minute_second` has been removed. |
| 39 | + Use `hour_minute_second_nanosecond` instead. |
| 40 | + - `DateTime` |
| 41 | + - The property `hour_minute_second` has been removed. |
| 42 | + Use `hour_minute_second_nanosecond` instead. |
| 43 | + - The property `second` returns an `int` instead of a `float`. |
| 44 | + Use `nanosecond` to get the sub-second information. |
11 | 45 |
|
12 | 46 | ## Version 4.4 |
13 | 47 |
|
|
0 commit comments