Skip to content

DDC-2045: Unit of work use all columns for insert #2724

doctrinebot opened this Issue Sep 27, 2012 · 3 comments

2 participants


Jira issue originally created by user coviex:

I use MySQL. And I'm OK with default values that will be assigned by DB for columns which values I don't set explicitly. But Doctrine seems to unable to skip some columns when building insert SQL query.

People suggest to use nullable flag to enable desired behaviour. And I don't see how it could help. I checked UnitOfWork.php and BasicEntityPersister.php. There is nothing about nullable.
And doc says that you cannot use custom persisters so far.

So why not track changes for unsaved entities as well, and don't force applications to generate more traffic with more SQL text and developers to set default values in entity constructors?

I would be glad if I'm mistaken and this feature is already implemented and you describe how to resolve the issue. Thanks


Comment created by @ocramius:

[~coviex] the nullable flag is a mapping used in columns. See

Also, Doctrine does not skip columns since default DB-side values are not supported by the ORM. To have default values, you usually set them in the entity's constructor.


Issue was closed with resolution "Won't Fix"


Comment created by coviex:

Marco, you should be ashamed of the way you treat issues.
RTFM answer when there is real and huge problem, seriously?!

@Ocramius Ocramius was assigned by doctrinebot Dec 6, 2015
@doctrinebot doctrinebot closed this Dec 6, 2015
@doctrinebot doctrinebot added the Bug label Dec 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.