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
