Jonathon For the A/R aging, there is no need to delete the table at the end, you could just delete all the records before you start over the next month. (Although if you wanted to split the work up to an unknown number of people, you would need some temporary files).
The purchacing is somewhat different (in the current use case) because the number of people assigned to purchasing this run is unknown until runtime. I could just create like 10 tables, and use the first x, but this seems pretty crude when the simple ability to dynamically create and destroy tables would make it easy and less work on the underlying db. So, is there really no way to dynamically create and delete tables? BJ sez there are some samples in the Manufacturing module. Is this already done there? (I havent looked at it because I don't have a need for Manufacturing atm). Skip -----Original Message----- From: Jonathon -- Improov [mailto:[EMAIL PROTECTED] Sent: Thursday, October 11, 2007 4:38 AM To: [email protected] Subject: Re: Odd Error I don't think Dynamic Views can help here. The "purchasing recommendation" is generated once, and is then presented again and again to the end-user. It is not generated every time the end-user needs to see it. How about creating a permanent table for both "purchasing recommendation" and aging AR? Why does it have to be a temporary table? When talking about "temporary data", I think it's still alright to store them in permanent tables. Login history is temporary enough. So is Visit(s). And others. I even stored "temporary passwords" in permanent tables, and just delete those passwords that are superseded by the creation of "permanent passwords". Jonathon vijay Si wrote: > I think Dynamic Views could help, but again u need to test performance > > On 10/11/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> Hi guys >> >> I have the need to develop a purchasing application that scans the last >> months sales, compares estimated shipping times and onhand quantities to >> generate purchacing recommendations (actually a good deal more complicated >> than this, but thats the gist). The resulting file is presented to the >> user >> who examines it over a few days and takes action on it. Then, it gets >> deleted. There is an undetermined number of files to be created >> (depending >> on how many people are doing purchasing at that time) all with the same >> structure. >> >> This means that I'll have to create a few temporary tables to hold the >> data >> and then delete them after the work is finished. >> >> I have a similiar need for aging Accounts Receivable. >> >> What is the recommended way of creating temporary tables and then deleting >> them when they are no longer needed? I know how to do this in SQL, just >> not >> in Ofbiz. >> >> Skip >> >> > > > ------------------------------------------------------------------------ > > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.488 / Virus Database: 269.14.7/1062 - Release Date: 10/10/2007 5:11 PM
