Hi, > The problem is with date, frequency and ends. With this info I can > know all the dates in which transactions occurs and use it to fill a > cashflow table. Doing things this way involves creating a lot of > structures(dictionaries, lists and tuples) and iterating them a lot. > Maybe there is a very simple way of solving this with the actual > schema, but I couldn't realize how. > > I think that the app would be easier to code if, at the creation of a > transaction, I could save all the dates in the db. I don't know if > it's possible or if it's a good idea.
You might want to look at python-dateutil, which lets you model repeating events. http://niemeyer.net/python-dateutil For Django, you might find that glamkit-eventtools is worth a look. I've used it to model holiday/vacation departure information for a travel site. You might find inspiration in its approach, even if you can't use it directly. Cheers, Dan -- Dan Fairs | [email protected] | www.fezconsulting.com -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
