http://qs321.pair.com?node_id=1057826


in reply to Re^3: DBI Prematurely Disconnecting
in thread DBI Prematurely Disconnecting

Also keep in mind that using RAISERROR in your SQL code to return a message can potentially cause the DBI/DBD code to think that an error has occurred, and cause the fetch loop to terminate.

Michael

Replies are listed 'Best First'.
Re^5: DBI Prematurely Disconnecting
by perldc (Initiate) on Oct 14, 2013 at 15:40 UTC
    That is true which is why I also tested with only select and update. Originally it was doing: 
    Select * from tempTable;
Update tempTable set done=1 where id=1;
Update tempTable set done=1 where id=2;
--connection gets broken

    [download]
    now with more results it executes fully: 
    Select * from tempTable;
Update tempTable set done=1 where id=1;
Update tempTable set done=1 where id=2;
Update tempTable set done=1 where id=3;
Update tempTable set done=1 where id=4;
Update tempTable set done=1 where id=5;

    [download]
    In the stored procedure the updates are within a while loop that generates the id so in this case no additional print or raiserror was being used.
[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom