Re: application design question
- From: Michael Moore <michaeljmoore@xxxxxxxxx>
- To: dmann99@xxxxxxxxx
- Date: Mon, 20 Jun 2011 10:49:39 -0700
David,
Thanks for the reply. I must not be too far off the mark in my approach.
Thanks for the tip about auto_drop. I'm not sure what that is, will have to
look it up. Anyway, the lack of responses tends to assure me that there is
not something really obvious I have missed.
Regards,
Mike
On Mon, Jun 20, 2011 at 9:00 AM, David Mann <dmann99@xxxxxxxxx> wrote:
> >Currently we have a Java GUI that invokes a pl/sql package procedure (A)
> >which does a lot of stuff and then returns control to the GUI. The trouble
> >is, it's taking too long. The 'stuff' it does is more suitable to a batch
> >job.
>
> Hi Michael,
>
> I waited a couple of days to see if anyone else would respond. I have
> worked with a few projects that needed this type of functionality for
> Java based web apps.
>
> There may be something out there but in our cases interface
> requirements were so specific that we just rolled our own. This was
> 8i/9i pre-DBMS_SCHEDULER days and we had to do all our own
> housekeeping to keep track of status of completed jobs and present to
> the user.
>
> Implementing the same thing would be a little easier today with
> DBMS_SCHEDULER by setting auto_drop to FALSE and submitting one-time
> jobs. I would write some PL/SQL to encapsulate the pre-job setup. This
> includes keeping some metadata to bridge the Scheduled Jobs with your
> application constructs (like the app userid of who submitted the job).
> I would also create a view to make it easier to present job status
> information to whatever front end will be looking for the data.
>
> -Dave
>
> --
> Dave Mann
> www.brainio.us
> www.ba6.us - Database Stuff - http://www.ba6.us/rss.xml
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
Other related posts:
