Re: next step on the EOEditingContext after succesfull save
Re: next step on the EOEditingContext after succesfull save
- Subject: Re: next step on the EOEditingContext after succesfull save
- From: Gustavo Pizano <email@hidden>
- Date: Tue, 24 Feb 2009 20:22:49 +0100
HEHE ok.. Im getting confused with Objective-C where memory
management, its a MUST DO!. hehe. Im gonan try to leave the core
running with as less errors as possible, and then dedicate myself to
enhance the front end, the client side, or should I call it the damn
presentation with AJAX, JS, and all those boys that takes my sleep
away all the nights. hehehe
Gustavo
On 24.2.2009, at 19:16, David Avendasora wrote:
On Feb 24, 2009, at 12:53 PM, Gustavo Pizano wrote:
Hello all.
Well, I was able to save the data I wanted to save,
Woo hoo! Success! Yipee thar be data in the database!
now I know there is an object in the session()editingContext, I
used that one so far, but what to do next, should I dispose that
object?
Why? Do you not need it anymore? Is it taking up too much memory?
keep it, why yes why no?, if I should delete it, how to, using the
dispose() method?
Yes, if you dispose of the editingContext it will make any EOs in
the EC available for Garbage Collection, but once your session times
out, the EC will get disposed of automatically.
Gustavo, you are over thinking WO. WO (and Java) deal with most of
these kind of housekeeping things for you. Need an object? Create it
or Fetch it. Use it every which way you want. When you're done, save
it to the DB if needed. Once that's done there's really no need to
actually dispose of the EO unless it is getting in the way.
Dave
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden