From 5123b428510ae704369bed7b438df9d3303b7113 Mon Sep 17 00:00:00 2001 From: Dane Springmeyer Date: Fri, 31 May 2013 13:36:29 -0700 Subject: [PATCH] Updated Api changes between v2.1 and v2.2 (markdown) --- Api-changes-between-v2.1-and-v2.2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Api-changes-between-v2.1-and-v2.2.md b/Api-changes-between-v2.1-and-v2.2.md index c45ef4d..c8c78b7 100644 --- a/Api-changes-between-v2.1-and-v2.2.md +++ b/Api-changes-between-v2.1-and-v2.2.md @@ -5,8 +5,8 @@ - Removed the `bind` option for datasources (#1654) ## Changed - - `[attr] != ''` now matches only empty strings. This syntax previously matched both empty strings and nulls but this behavior was unintended and buggy given that Mapnik has supported a `null` type since 2.0.0. If you wish to filter out all `attr` values that are not `empty strings` or `null` or `false boolean type` then you can do `[attr]` or `[attr] != '' and [attr] != null and [attr] != false` - Proj4 init errors due to invalid `srs` values will now cause exceptions when a map is loaded from XML as well as when encountered during rendering. The latter will very unlikely happen now that validation is done at map loading time. Previously errors were not reported except at render time and only as warnings printed to stderr (#646) + - `[attr] != ''` now matches only empty strings. This syntax previously matched both empty strings and nulls but this behavior was unintended and buggy given that Mapnik has supported a `null` type since 2.0.0. If you wish to filter out all `attr` values that are not `empty strings` or `null` or `false boolean type` then you can do `[attr]` or `[attr] != '' and [attr] != null and [attr] != false` No longer the case for 2.2 release, due to backwards compatibility fix as per https://github.com/mapnik/mapnik/issues/1859 ## Added - Added Logging framework documentation synced with 2.2 status: https://github.com/mapnik/mapnik/wiki/Logging