CoreData:User creates new record, but then cancels = trash.. thoughts...

[j3rm]

Hi all,
I need some feedback on something I would like to improve in my apps.
I have several Business apps, and they use CoreData. When a user wants to add a new record, I create one and save it to the database, then show the ViewController to edit the record. The side affect of this approach is that , if the user cancels, then there is a "half baked" record hanging out there, that shows up and confuses the user.

Ideally, I would like for the record to no longer exist if the user hits cancel.
I have some ideas but I don't think they are good solutions, as they open the door for more bugs. Whats the right way to do this?

I appreciate any insight.
Thanks

[BrianSlick]

Solution I haven't tried yet: specify nil for the context when creating the object. Insert it into the context when the user saves.

Solution I have done: create a placeholder instance, with some kind of flag that keeps it out of regular usage. The edit screen deals with this instance. When the user saves, create a new instance and copy over the necessary properties from the placeholder.