An idea… If the transaction object knows the previous one, the get balance
method would return the current transaction amount +++plus the previous
transaction (if it is not nil). It would be more than an array, but a list…
But in core data it is not that simple, I guess.
On Wed, Jun 18, 2008 at 7:5
It was not that clear on the tutorial. =)
I was studying Objective C and I had started to implement the classes of my
project by hand when I saw that tutorial about Core Data. That was when I
moved my "DTO" to Core Data. I think I have to make them by hand.
And about the amount/balance and so on…
On Jun 18, 2008, at 13:04, Ben Trumbull wrote:
*Amount* is an calculated field and it depends on the previous
transactions.
I don't know how to do it! It is not a value I can save on
database, for
example, because it changes all the time (I guess I have to mark the
transient field at Core D
On Wed, Jun 18, 2008 at 7:33 PM, Thiago Rossi <[EMAIL PROTECTED]> wrote:
> *Amount* is an calculated field and it depends on the previous transactions.
> I don't know how to do it! It is not a value I can save on database, for
> example, because it changes all the time (I guess I have to mark the
*- I'm a Java programmer who wants to migrate to ObjC/Cocoa.*
Welcome.
Unlike some of the others, I don't think Core Data requires an
advanced degree in Cocoa. However, in my experience, trying to learn
both Cocoa Bindings and Core Data simultaneously overwhelms many
people new to Cocoa.
> Can anyone please help me?
No. At least not at present. There have been many discussions
(several very long ones recently) about the fact that - as stated in
the documentation - Core Data is most emphatically NOT a beginner
technology. Any effort spent trying to help you run before you can
cra
1. You really need to master the basics of Cocoa before you tackle
Core Data.
2. I would move "amount" over on the "Account" entity, and rename it
"balance".
3. See #1.
Hal
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not
