Hi,

My mistake, I did not make my assumption of a large number of users clear.
It is also quite possible that this is much less of a problem with firebird
than other databases.

Thanks for the example

david jencks

On 2001.06.07 14:55:06 -0400 Alexander V.Nevsky wrote:
> --- In IBDI@y..., David Jencks <davidjencks@e...> wrote:
> > Hi,
> > I have no idea what development environment you are in, however
> leaving a
> > transaction open for any length of time is almost always a terrible
> idea.
> >
>
> Hi, David. I often here it, but can't see in my own practice. My
> application starts read only read commited transaction on loading an
> all day almost all select are done in this transaction. All changes
> and additional short selects around changes are made in short snapshot
> transactions. I have 15 active users and about 20 read-only ones.
> Dayli they perform about 30 000 transactions, sweep is turned off and
> performed at night by cron to normalize OIT. I really can't see any
> performance degradation. Can you explain what is wrong with such
> application structure?
>
> Best regards.
>
>
> Community email addresses:
> Post message: IBDI@yahoogroups.com
> Subscribe: IBDI-subscribe@yahoogroups.com
> Unsubscribe: IBDI-unsubscribe@yahoogroups.com
> List owner: IBDI-owner@yahoogroups.com
>
> Shortcut URL to this page:
> http://www.yahoogroups.com/community/IBDI
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>