At 05:02 AM 5/09/2003 +0000, you wrote:

>--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
>wrote:
> > At 01:50 AM 5/09/2003 +0000, you wrote:
> > >hi,
> > >
> > >I am having the above error code while I issueing a select query
>from
> > >isql:
> > >select count(*) from table1;
> > >
> > >it returns:
> > >Statement Failed, SQLCODE= -913
> > >deadlock
> > >
> > >
> > >What should I do to clear the deadlock? and what should I do to
>avoid
> > >this error happen again?
> >
> > This is weird. It shouldn't happen at all in isolation levels
>SNAPSHOT or
> > READ COMMITTED. isql runs DML in SNAPSHOT by default. Writers in
>these
> > isolation levels don't block readers, so you should never get a
>lock
> > conflict just counting rows.
> >
> > Can you provide some information about what database and version
>you are using?
> > What else was going on the database 1) inside your isql session 2)
>outside it?
> >
> > heLen
>
>I am runing firebird 1.0 in Sun Sparc (S0-V1.0.0.796 Firebird 1.0).
>Previously I have deadlock error when I update a table thru my
>application. After get the error, I terminated the application by
>using CTRL-C, since it is a C-program application. Then, I issued
>select count(*) command thru isql, and got this error -913.

Then, after a timeout period, the server would have rolled back the broken
transaction. You were probably just too quick for it.

How to avoid it? Don't crash out of connected client applications!! Learn
to love deadlocks - just write applications that do the right thing with
them.

heLen