silverstripe-framework/docs/en/changelogs/3.0.6.md

# 3.0.6 (Not yet released)

## Upgrading

 * If you have created your own composite database fields, then you shoulcd amend the setValue() to allow the passing of an object (usually DataObject) as well as an array.
NEW: Added DataObject::getQueriedDatabaseFields() as faster alternative to toMap() API: CompositeDBField::setValue() may be passed an object as its second argument, in addition to array. These changes provide a 15% - 20% performance improvement, and as such justify an small API change in the 3.0 branch. It will likely affect anyone who has created their own composite fields, which is fortunately not all that common. 2013-04-21 03:18:18 +02:00			`# 3.0.6 (Not yet released)`

			`## Upgrading`

			`* If you have created your own composite database fields, then you shoulcd amend the setValue() to allow the passing of an object (usually DataObject) as well as an array.`