Re: Pro*c Connection to db

Well, if the Pro*C app was set up as some form of server program, it could keep the DB connection open. Depending on where the input is coming from, you might have to use some Clint/Server plumbing, like CORBA, DCE, EJB, etc. There might be some small delay in establishing the C/S connection, depending on the technique used. You could also poll a directory area, where image files are moved (not copied) for processing.

Peter

Tom Zamani wrote:
>
> we need to archive images in the database, they have a type of long row,
> about 100k each.
>
> Kenneth C Stahl <BlueSax_at_Unforgettable.com> wrote in message
> news:382839E1.D4A84ED5_at_Unforgettable.com...
> > Tom Zamani wrote:
> > >
> > > Hi there,
> > > We have a Pro*C program to archive data, each time this module is called
> it
> > > will login to database and does the archiving, is there any way which I
> > > could make it to login once, so I can avoid login to the database all
> the
> > > time.
> > > I could put the all logic in the Pro*C program and let it run all the
> time.
> > >
> > > The other method is to make the precompile the pro*c get the c code and
> > > make it as external procedure call.
> > > in either way it will have to relogin to the database.
> > >
> > > Is there any way to avoid this?
> > > Tom
> >
> > Could you make another stab at explaining this? "The other method is to
> > make the precompile the pro*c get the c code and make it as external
> > procedure call." doesn't make much sense.
> >
> > Try to explain what you are attempting to "archive".
Received on Wed Nov 10 1999 - 13:20:24 CET