|
1 |
| -Build 5.1.1 |
| 1 | +Build 5.1.2 |
| 2 | +============================= |
| 3 | + |
| 4 | +Release notes - NHibernate - Version 5.1.2 |
| 5 | + |
| 6 | +** Bug |
| 7 | + |
| 8 | + * #1660 Wrong CopyTo implementation |
| 9 | + * #1650 Cannot use cache.use_sliding_expiration in hibernate.cfg.xml |
| 10 | + * #1585 Hashset unsupported by SetParameterList |
| 11 | + |
| 12 | +** Task |
| 13 | + |
| 14 | + * #1668 Merge 5.0.5 into 5.1.x |
| 15 | + * #1664 Release 5.1.2 |
| 16 | + * #1659 Merge 5.0.4 into 5.1.x |
| 17 | + |
| 18 | +As part of releasing 5.1.2, a missing 5.0.0 possible breaking change has been added about future queries with data |
| 19 | +providers not actually supporting them. See 5.0.0 possible breaking changes. |
| 20 | + |
| 21 | + |
| 22 | +Build 5.1.1 |
2 | 23 | =============================
|
3 | 24 |
|
4 | 25 | Release notes - NHibernate - Version 5.1.1
|
@@ -319,6 +340,10 @@ Build 5.0.0
|
319 | 340 | the dialect. They resolve to 4000 length string and (28, 10) precision/scale decimals by default, and are
|
320 | 341 | trimmed down according to dialect. Those defaults can be overridden with query.default_cast_length,
|
321 | 342 | query.default_cast_precision and query.default_cast_scale settings.
|
| 343 | + * Future queries with data provider not actually supporting them (not supporting mutliple queries in a single |
| 344 | + SQL command) are no more immediately executed at the .Future call. They are executed only when directly |
| 345 | + enumerated or when their IFutureEnumerable.GetEnumerable method is called. (This aligns them with the behavior |
| 346 | + of FutureValue.) |
322 | 347 | * Dialects are now configurable. If you instantiate a dialect directly, make sure you call its Configure
|
323 | 348 | method, with as argument the properties of a NHibernate Configuration object. You may use instead
|
324 | 349 | Dialect.GetDialect methods, which configure the dialect before returning it.
|
|
0 commit comments