Hi, Michael, thanks for your help. Could you tell me is there any document to this? I am asking because we are experiencing memory leak and I am suspicious that our daily DBI script is causing the memory leak because the statement handler is not closed properly, etc,etc.
Thanks -----Original Message----- From: Michael A Chase [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 16, 2002 2:16 PM To: Shao, Chunning Cc: [EMAIL PROTECTED] Subject: Re: Raise Error option, can we trust it? A die() call shuts down the entire script. Everything gets closed during shutdown. -- Mac :}) ** I normally forward private questions to the appropriate mail list. ** Give a hobbit a fish and he eats fish for a day. Give a hobbit a ring and he eats fish for an age. ----- Original Message ----- From: "Shao, Chunning" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, January 16, 2002 07:21 Subject: Help: Raise Error option, can we trust it? Reading from the man page on unix machine, it only says that When set "on", any method which results in an error will cause the DBI to effectively do a `die("$class $method failed: $DBI::errstr")', where `$class' is the driver class and `$method' is the name of the method that failed. But it did not mention that whether it will close the connection with the database, close the statemnet handle, return the resource to the operating system, etc. Can we trust RaiseError On option?
