StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17718299
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-07-18T08:24:38.037
FavoriteCount
0
LastActivityDate
2013-07-18T08:42:05.493
LastEditDate
2013-07-18T08:42:05.493
LastEditorUserId
2594491
OwnerUserId
2594491
ParentId
6855796
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
When using (from <a href="http://forums.mysql.com/read.php?51,256433,256478" rel="nofollow">MySQL forum</a>) <pre><code>use Sys::SigAction qw( set_sig_handler ); eval { my $hsig = set_sig_handler( 'ALRM', sub { my $canceled = 1; die; }, { mask=>[ qw( INT ALRM ) ] ,safe => 0 } ); alarm($timeout); ... alarm(0); } </code></pre> I noticed that any subsequent calls made to <code>sleep($delay)</code> with <code>$timeout</code> shorter than <code>$delay</code> would end up with the script execution being terminated, and the print of "<code>Alarm clock</code>". The workaround I've found is to call <code>alarm()</code> again but with an improbably large value (3600), and cancel that alarm right after. <pre><code>eval { alarm(3600); print " .... Meeeep ...."; # Some trace alarm(0); }; </code></pre> Then I can use <code>sleep()</code> with no interference anymore. Example below (live code snippet): <pre><code>sub unmesswithsleep { eval { alarm(3600); &tracing (8, " .... Meeeep ...."); alarm(0); }; } sub lockDBTables { return (0) unless ($isdbMySQLconnect); my $stm = qq { LOCK TABLES myBIGtable WRITE }; my $timeout = 60; # This is the timer set to protect against deadlocks. Bail out then. eval { my $h = set_sig_handler( 'ALRM', sub { my $canceled = 1; die; }, { mask=>[ qw( INT ALRM ) ] ,safe => 0 } ); alarm($timeout); my $res = $dbmyh->do($stm) + 0; alarm(0); # Reset alarm }; if ( $@ =~ m/Die/i ) { $isdbTabledlocked = 0; &tracerr (0, "FATAL: Lock on Tables has NOT been acquired within ${timeout}s. Lock is set to <$isdbTabledlocked>."); &unmesswithsleep(); # MUST be called each time alarm() is used return (0); } else { $isdbTabledlocked = 1; &tracing (2, " Good: Lock on Tables has been acquired in time. Lock is set to <$isdbTabledlocked>."); &unmesswithsleep(); # MUST be called each time alarm() is used return (1); } # Can use sleep() now. } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat else can i do 'sleep' when the sleep() can't work well with alarm?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USTVNshack
UserOwnerUserId
1. USTVNshack
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.