DBI don't respond after SQL execution failure

Erland,
	I checked in the SQL Profiler, but the data is garbled or
garbage in the SQL Profiler.

Is there any way we can stop the DBI from getting hung when
such data is
supplied or recover atleast. 
 
krishna Talinki

-----Original Message-----
From: Erland Sommarskog [mailto:esquelsommarskog.se] 
Sent: Thursday, December 29, 2005 12:08 PM
To: krishna Talinki
Subject: Re: DBI don't respond after SQL execution failure

>I am trying to solve the hanging issue after the execute
failure.
>
>We have UTF8 string data that represents Japanese
characters.
>When we check the data size before sending it to the
$sth->execute(),
>the data size is smaller than the size of the table
column.
>We are depending on the PerlIO Encode module to convert
the data to
>NVARCHAR(UCS2) before sending it to SQL Server.

Have you checked with Profiler, what DBI actually sends to
SQL Server?
It sounds strange that the length of the strings would
change when it's
converted to UCS-2. That sounds as if the conversion is done
properly.

>If I have same error with English data in UTF8, the DBI
calls are not
>hanging after that.

Why DBI bails out I have no idea.

/Erland

_______________________________________________
Perl-Win32-Database mailing list
Perl-Win32-Databaselistserv.ActiveState.com
To unsubscribe: http:/
/listserv.ActiveState.com/mailman/mysubs