Subject | Some issues with deleting from MON$STATEMENTS |
---|---|
Author | Mathias Dellaert |
Post date | 2007-12-04T08:30:13Z |
Hi all,
I realise that since this question pertains to a beta version that this
may not be the right place to as kit. If so, please accept my apologies
and direct me to the correct place.
I'm having some trouble with ending stuck queries by deleting the
appropriate lines from MON$STATEMENTS with Firebird 2.1 beta 2 (on
winxp, if that matters). I'm using for example the following statement:
DELETE FROM MON$STATEMENTS WHERE MON$STATEMENT_ID IN (1591058,1591416);
(different WHERE clauses have given the same result). When
executing/committing that I get a message that 2 rows were affected, but
upon checking they will often still be there. The statements tend to
have the following special characteristics:
- Their originating connection terminated suddenly (ctrl-alt-del kill)
- They were waiting for a lock when they got terminated.
Any clues as to what I could do?
Thanks in advance
[Non-text portions of this message have been removed]
I realise that since this question pertains to a beta version that this
may not be the right place to as kit. If so, please accept my apologies
and direct me to the correct place.
I'm having some trouble with ending stuck queries by deleting the
appropriate lines from MON$STATEMENTS with Firebird 2.1 beta 2 (on
winxp, if that matters). I'm using for example the following statement:
DELETE FROM MON$STATEMENTS WHERE MON$STATEMENT_ID IN (1591058,1591416);
(different WHERE clauses have given the same result). When
executing/committing that I get a message that 2 rows were affected, but
upon checking they will often still be there. The statements tend to
have the following special characteristics:
- Their originating connection terminated suddenly (ctrl-alt-del kill)
- They were waiting for a lock when they got terminated.
Any clues as to what I could do?
Thanks in advance
[Non-text portions of this message have been removed]