Jonathon No, I think what he wants is a table to hold temporary results. The aging he is talking about (I think) is calculating interest due on past due accounts. This changes every 24 hours and the table data itself changes as invoices are paid/added.
In addition, it is helpful to build a table holding the totals from above for collections. The way I have done it in the past is to create a temporary table to hold the sums of the amounts 30 days past due, 45 days past due (cause that seems to be the sweet spot for collections), and 60 days past due. This table is then used to help the collections person and for reporting. It is regenerated for each cycle and then deleted. Skip -----Original Message----- From: Jonathon -- Improov [mailto:[EMAIL PROTECTED] Sent: Sunday, September 16, 2007 4:25 AM To: [email protected] Subject: Re: Temporal Tables Hi Jose Diaz, I'd advise against having such a temporary table. The Entity Engine's "retrieve data from cache" functions could help you. Perhaps you're worried that a plain old query (even via <view-entity>) into the actual data table will impact performance? Perhaps you need to make very many queries that report the latest (daily?) data? The cache will help. There's no point creating a separate table called say SomeUpToDateCache that acts simply as a cache to hold the latest data. The Entity Engine's cache will do that just fine, I think. Jonathon Jose Diaz wrote: > Please, let me know some advice about this: > > I need work with temporal tables, it because I don't want to create a table for save data and next delete it. Create your entity, update the entitygroup, etc. > > I am updating the aging report , because the data in the future will be bigger. > Then I am doing a service that load the data all the days (midnight) in a table and i only read of it for show the aging report. > > For it, I need a temporal table that save the data of the service: > > Map invoicesByDSO = AccountsHelper.getUnpaidInvoicesForCustomers(organizationPartyId, daysOutstandingPoints, asOfDateTime, delegator); > Next, group the data in it format more simple : > > LocationAccountCurrent< 3031 - 6061 - 90> 90Total > 3 Oaks Car Wash - MasterN746109010 - - - - 327.74 > 7035 PROPERTIES 1 - MasterK300750001 - 21.06 - - - 1,321.06 > 7035 PROPERTIES 2 - MasterT931471026 - 19.98 - - - 219.98 > A B S Graphics - MasterQ268095009 - - - - 4,162.01 > > In conclusion, is possible create temporal tables in a java service?? > > Jose Diaz > > > > ----- Original Message ----- > From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> > Sent: Sat, 9/15/2007 2:09am > To: [email protected] ; Cameron Smith <[EMAIL PROTECTED]> > Subject: Ofbiz and Dojo > > Anyone have any comments on using Dojo with Ofbiz, especially the .9 > release? > > I see that the .9 release is like half the size of the .4 release > > Skip > >
