Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DCOM-77: add a method to force removal of any unmapped data on flush for a given object #678

Open
doctrinebot opened this issue Nov 16, 2011 · 1 comment
Open

DCOM-77: add a method to force removal of any unmapped data on flush for a given object #678

doctrinebot opened this issue Nov 16, 2011 · 1 comment
Assignees
@beberlei
Labels
New Feature

Comments

@doctrinebot
Copy link

Jira issue originally created by user @lsmith77:

in order to ensure that any unmapped fields are set to their defaults or removed in the case of nosql right now there is no way to do this except with 2 flush calls: aka removeflush, persistflush

there should be some way to do this in one flush
@Majkl578
Copy link
Contributor

Not really sure what this is about, thoughts @lsmith77 @Ocramius?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@beberlei beberlei

Labels
New Feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@beberlei @Majkl578 @doctrinebot