silverstripe-framework/docs/en/04_Changelogs/4.4.0.md

# 4.4.0

## Overview {#overview}

 - [Correct PHP types are now returned from database queries](/developer_guides/model/sql_select#data-types)
 
## Upgrading {#upgrading}

 - dev/build is now non-destructive for all Enums, not just ClassNames. This means your data won't be lost if you're switching between versions, but watch out for code that breaks when it sees an unrecognised value!

## Changes to internal APIs

 - `PDOQuery::__construct()` now has a 2nd argument. If you have subclassed PDOQuery and overridden __construct() 
   you may see an E_STRICT error
DOC: Added documentation for strict type changes 2018-11-08 23:08:36 +01:00			`# 4.4.0`

			`## Overview {#overview}`

			`- [Correct PHP types are now returned from database queries](/developer_guides/model/sql_select#data-types)`

			`## Upgrading {#upgrading}`

FIX: Make all enums non-destructive, not just ClassName This change also renders a portion of DBSchemaManager irrelevant, that destructively “fixes” old values. This is in keeping with the non-destructive principle of dev/build, and some suggestions to move away from enum fields altogether. Fixes https://github.com/silverstripe/silverstripe-framework/issues/1387 2018-10-08 06:07:50 +02:00			`- dev/build is now non-destructive for all Enums, not just ClassNames. This means your data won't be lost if you're switching between versions, but watch out for code that breaks when it sees an unrecognised value!`
DOC: Added documentation for strict type changes 2018-11-08 23:08:36 +01:00
			`## Changes to internal APIs`

			- `PDOQuery::__construct()` now has a 2nd argument. If you have subclassed PDOQuery and overridden __construct()
			`you may see an E_STRICT error`