From: <no...@so...> - 2001-02-21 02:09:15
|
Bug #133124, was updated on 2001-Feb-19 11:46 Here is a current snapshot of the bug. Project: Firebird Category: Core Engine Status: Open Resolution: None Bug Group: Confirmed Bug Priority: 5 Submitted by: dimitr Assigned to : nobody Summary: Connection lost during the bad SQL code execution Details: Platform: WinNT, Win2k Version: 0.9-3 & 0.9-4 Tools: IB_WISQL, QuickDesk If I try to alter domain with a bit wrong syntax like: alter domain domain_name set type smallint; where 'set' is illegal, the connection between server and client is lost with the following well-known error: Unable to complete network request to host "host_name". Error writing data to the connection. unknown Win32 error 10054 The problem seems to be the client's one. Maybe it is not very serious bug, but any request should have predictable result, IMHO. Follow-Ups: Date: 2001-Feb-20 18:10 By: helebor Comment: Here's another example, reported to the Mers list by Marco Schluenss <pro...@sc...>: my problem is to declare the attached trigger in my news-db. when declaring it, interbase crashes immediatly. does somebody has any hints? the suspicious trigger: CREATE TRIGGER AH_DELETE_THREAD FOR NWS_ART_HEADER BEFORE DELETE AS DECLARE VARIABLE tht INTEGER; BEGIN FOR SELECT nws_thread_total, nws_thread_unread FROM nws_thread WHERE nws_thread_idx = OLD.nws_art_thread_id FOR UPDATE OF nws_thread_total, nws_thread_unread INTO tht AS CURSOR thcrs DO IF (tht > 1) THEN IF (old.nws_art_read like 'T%') THEN UPDATE nws_thread SET nws_thread_total = nws_thread_total -1 WHERE CURRENT OF thcrs; ELSE UPDATE nws_thread SET nws_thread_total = nws_thread_total -1, nws_thread_unread = nws_thread_unread -1 WHERE CURRENT OF thcrs; ELSE DELETE FROM nws_thread WHERE CURRENT OF thcrs; END -- ------------------------------------------------------- Date: 2001-Feb-20 17:58 By: robocop Comment: This is a fatal bug in the server. The server itself dies with a memory error. The construction alter domain domain_name set type smallint; kills it immediately. Thanks for reporting it. I couldn't find another combination that causes the same effect. C. ------------------------------------------------------- Date: 2001-Feb-20 01:37 By: nobody Comment: Oops, I was wrong. The problem is defenitely the server's one because *all* active client connections become broken. So for now, it is very easy way to forcibly disconnect all users that are currently attached to the server without crashing or restarting the one. Dmitry ------------------------------------------------------- For detailed info, follow this link: http://sourceforge.net/bugs/?func=detailbug&bug_id=133124&group_id=9028 |