iOS patterns for creating object before saving?

Question

I am pretty new to iOS and I am currently designing the "Create a new event" page for my app.

Some info:

1. A user can click on create a new event and then press back to cancel creating this new event. (I am using UINavigationController)
2. 1 video can be attached to a particular event.
3. A user can create a new event, record a video, then decides not to go ahead with saving it (by pressing back)
4. Each event must generate a uuid. This uuid is required to prevent entity collision between different clients creating events and submitting them to the server.
5. Each video captured is named uuid.mov for storing into the file system before the event is uploaded to the server.

Coming from a rails background, I am used to doing the following:

1. When the user click on "Create new event page", an event is created but not saved to the db.
2. The user then enters attributes to the page and decides if he/she wants to commit
3. When commit take places, the event is attributed with the information provided. The event is then saved.

However, I don't believe Core Data has an API that allows the developer to create an entity without saving it. Currently, I am doing something like this:

1. When the user visits the "create new event page", an empty object is created and stored into the db. The reference to the event instance is passed to the Controller of the create a new event page.
2. When the user has inputted all the information and shot a video (the uuid is created at awakeFromInsert and is set during 1), saving is merely setting the entity with the required attribute.
3. If the user decides to cancel creating an event, I am checking whether cancel is pressed. if it is, both the event and the video file is deleted.

Code to check if Cancel is pressed.

- (void)viewWillDisappear:(BOOL)animated {
    [super viewWillDisappear:animated];
    if (![[self.navigationController viewControllers] containsObject:self]) {

This is a bit complicated to be honest. Do you guys have a better suggestion?

Answer 1

It actually works as you described Rails working: new objects aren't saved to the persistent store until you commit them (via NSManagedObjectContext's save: method).

See the Creating and Deleting Managed Objects section of the Core Data Programming Guide. Excerpting...

Simply creating a managed object does not cause it to be saved to a persistent store. The managed object context acts as a scratchpad. You can create and register objects with it, make changes to the objects, and undo and redo changes as you wish. If you make changes to managed objects associated with a given context, those changes remain local to that context until you commit the changes by sending the context a save: message. At that point—provided that there are no validation errors—the changes are committed to the store.