database design - Modeling Recurring Transactions in Core Data -


i'm having hard time coming conceptual model recurring transaction scheme in core data. far have:

1) billmaster entity (referenced above) has attributes "due date" "title" etc.
2) billentry entity children of master bill, actual bills see on calendar. these point master data due date, title, , keep track of whether instance of bill has been paid or not.

the problem is, i'm going need duplicate these masters , create recurring children entries in way that's efficient, 1 every time bill recurs. i'm not sure when entry generation should occur, , how far out should go for. don't want accidentally re-generate these when it's not necessary to. maybe there's smarter way model out i'm not thinking of.

if there suggestions of have, or maybe reading material goes on conceptual things this, i'm open anything. have understanding of core data in general (fairly good, no expert means) of these more complex models still throw me loop.

there's 5 different "core data" comes up. macos ?

but anyway, seems question generic, not specific core data. basically, assuming billmaster correct, somewhere in app, need button "generate bills". project billmaster billentry, whatever billmasters billable right now.

  • just one, if monthly, , next month has not been billed
  • otherwise pickup iterations since last time user hit button
  • and none @ if keep hitting button (the next projection find no billmasters billable).

Comments

Popular posts from this blog

Add email recipient to all new Trac tickets -

400 Bad Request on Apache/PHP AddHandler wrapper -

php - Change action and image src url's with jQuery -