> -----Original Message-----
> From: Jerome Bouvattier [mailto:JBouvattier@...]
> Sent: 10. maj 2004 13:24
> To: firebird-support@yahoogroups.com
> Subject: Re: [firebird-support] How to prevent external
> developer teams from issuing long running transactions ?
>
> Hi Alan,
>
> > > Hello,
> > >
> > > When developing my OLTP system, I'm putting great care to
> avoid long
> > > running transactions.
> > >
> > > However, I might have to give access to other developpers for
> > > different projects. Those developpers are not used to
> IB/FB and the
> > > "Long running transaction" issue.
> > > I can "advise" them not to issue long running tx, but I
> can't "force"
> them
> > > to do so while coding or even using an admin tool to look at data.
> > >
> > > Is there something I can do at the DB level to prevent
> the problem ?
> > >
> > > Thanks for your help.
> > >
> > > --
> > > Jerome
> >
> > My best advice - get those developers off your production database.
> > Give them a copy for them to do what they want in the way
> of testing.
> > Alan
> >
>
> If it's for read-only data that needn't to be up to date, I
> could pump data in some kind of warehouse db.

If they only need read access then they could use "Read only, read commited
transactions". Long running "Read only, read commited transactions" are not
a problem as far as I am informed.

-
SMN