Odd Method behaviour

[Meredi86]

Hey guys, i have a small problem with a method and how it affects my core data.

The line in question is this:

// set status to 1 here: 1 = complete and READY to sync
[self.referringObject setValue:[NSNumber numberWithInt:1] forKey:@"status"];

So this sets a value of 1 to the current object held in "self.referringObject". but i dont have this directly in a button or method. It is set in a void method that is designed to post data to a server.

In order to call this at the time of my (or the users) choosing i have it called from a button:

- (IBAction) test: (id) sender {
   
    [self createInvoiceItemsString];
}

But after pressing the button, if i use an SQLite browser to look up my database i can see that "status" hasnt been changed from 0 to 1.
Here is the twist though: If i call the exact same method from my viewDidLoad (in the same class) then it will alter it to be a 1 and everything will be set ok.

I dont mind that much if i have to set this in viewDidLoad, but it would potentially cause some problems with data management and as such it would be much better suited if the button was to set this. I have tried moving that line of code to the button so that sets it directly but this also doesnt change anything.

Any idea as to why this would work from viewDidLoad but not from a button?

Thanks in advance Joe

[dany_dev]

I don't understand how is related that code to SQLite.....

however are you sure that all the code is running? use some NSLog...

[Meredi86]

Its related to SQLite because i am saving to core data - an SQLite database. So an SQLite browser such as "SQLite Database Browser" allows me to look at what has and hasnt been saved. An easy and effective way to check up on your database. The actual code itself has nothing to do with the SQLite language apart from it being the line of code that sets a value to my entity in core data.

Yes i am 100% sure that the line is being run, i have checked with both breakpoints and NSLogs. In both instances (call from viewDidLoad and from the IBAction) the line is executed. But if its from the button it just doesnt do anything

[Duncan C]

Originally Posted by Meredi86

Hey guys, i have a small problem with a method and how it affects my core data.

The line in question is this:

// set status to 1 here: 1 = complete and READY to sync
[self.referringObject setValue:[NSNumber numberWithInt:1] forKey:@"status"];

So this sets a value of 1 to the current object held in "self.referringObject". but i dont have this directly in a button or method. It is set in a void method that is designed to post data to a server.

In order to call this at the time of my (or the users) choosing i have it called from a button:

- (IBAction) test: (id) sender {
   
    [self createInvoiceItemsString];
}

But after pressing the button, if i use an SQLite browser to look up my database i can see that "status" hasnt been changed from 0 to 1.
Here is the twist though: If i call the exact same method from my viewDidLoad (in the same class) then it will alter it to be a 1 and everything will be set ok.

I dont mind that much if i have to set this in viewDidLoad, but it would potentially cause some problems with data management and as such it would be much better suited if the button was to set this. I have tried moving that line of code to the button so that sets it directly but this also doesnt change anything.

Any idea as to why this would work from viewDidLoad but not from a button?

Thanks in advance Joe

Try adding a call to your managed object context's save method. That should force Core Data to commit unsaved changes to the "persistent store" (in your case, your SQL database.)

[Meredi86]

Duncan: Thanks, i couldnt put the line into the save method. that was happening at a different point much earlier in the code, and to add it there would have again messed up the data integrity.

However i found this hiding at the bottom of my viewDidLoad:

NSError *errorOne;
    [self.managedObjectContext save:&errorOne];

So i moved that out of the viewDidLoad and dropped it right under that one line (the only line that makes a change at this point so the only line that needs the save) And now it works - sweet. Usually something tiny that i have missed with these things!

If you dont save you dont get :P

Thanks again Duncan, much appreciated