---
title: "Important: #69084 - Adding Extbase Objects with NOT NULL columns has changed"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:important-69084"
source: "Changelog/7.5/Important-69084-AddingExtbaseObjectsWithNOTNULLColumnsHasChanged.rst"
typo3-version: "7.5"
typo3-major: 7
type: "important"
issue: 69084
forge: "https://forge.typo3.org/issues/69084"
tags: ["Database", "ext:extbase"]
rendered: "2026-09-20T18:31:11+00:00"
---

# Important: #69084 - Adding Extbase Objects with NOT NULL columns has changed {#important-69084}

See [forge#69084](https://forge.typo3.org/issues/69084)

## Description {#description}

To better support databases that don't silently convert `NULL` values to
an empty default value for database columns defined as `NOT NULL` the
`insertObject()` method tries to determine the appropriate value for a column.

Extbase object properties that have a value of `NULL` will be skipped when
preparing the record to enable the DBMS default value to be used. This behavior
has not changed compared to TYPO3 CMS 7.4 but allows proper support for DBMS that
are strict about `NOT NULL` columns by defining appropriate default values for
properties in the models.

Example database schema:

```sql
CREATE TABLE tx_blogexample_domain_model_blog (
	title varchar(255) DEFAULT '' NOT NULL
);
```

Example model definition:

```php
class Blog extends \TYPO3\CMS\Extbase\DomainObject\AbstractEntity {
	/**
	 * The blog's title.
	 *
	 * @var string
	 */
	protected $title = '';
}
```