fetchrow_hashref failed problem

dcunningham has asked for the wisdom of the Perl Monks concerning the following question:

Replies are listed 'Best First'.
Re: fetchrow_hashref failed problem by mje (Curate) on Jul 21, 2015 at 07:57 UTC
What you described doesn't make sense to me unless DBD::mysql or DBI is broken as execute is supposed to return undef on an error. What do you get if you change the if statement to assign the execute return to a variable and then dump it when fetchrow_hashref fails? Have you tried enabling DBI tracing to see what is going on?	[reply]
Re: fetchrow_hashref failed problem by 1nickt (Canon) on Jul 21, 2015 at 01:17 UTC
what does the sql say? What is the return value of the execute call? The way forward always starts with a minimal test.	[reply] [d/l]
Re^2: fetchrow_hashref failed problem by dcunningham (Sexton) on Jul 21, 2015 at 01:34 UTC
We get: `DBD::mysql::st execute failed: Deadlock found when trying to get lock; + try restarting transaction at /path/to/Database.pm line 313. DBD::mysql::st fetchrow_hashref failed: fetch() without execute() at / +path/to/Database.pm line 315.` [download] Now the deadlock is not unexpected - we just want to deal with it gracefully and not get the fetchrow_hashref error.	[reply] [d/l]
Re^3: fetchrow_hashref failed problem by 1nickt (Canon) on Jul 21, 2015 at 02:23 UTC
are you sure they are from the same call? Assuming you are looping through something, could this be relevant from the docs? `If execute() is called on a statement handle that's still active ($sth +->{Active} is true) then it should effectively call finish() to tidy +up the previous execution results before starting this new execution.` [download] The way forward always starts with a minimal test.	[reply] [d/l]
Re^3: fetchrow_hashref failed problem by runrig (Abbot) on Jul 21, 2015 at 17:13 UTC
Is RaiseError set? If you get the deadlock error, you should not fetch again, you should start the whole transaction over again.	[reply]
Re: fetchrow_hashref failed problem by vinoth.ree (Monsignor) on Jul 21, 2015 at 05:46 UTC
If you are using InnoDB or any row-level transactional RDBMS, then it is possible that any write transaction can cause a deadlock, even in perfectly normal situations. Larger tables, larger writes, and long transaction blocks will often increase the likelihood of deadlocks occurring. The only way to truly handle deadlocks is to write your code to expect them. This generally is not very difficult if your database code is well written. Often you can just put a try/catch around the query execution logic and look for a deadlock when errors occur. If you catch one, the normal thing to do is just attempt to execute the failed query again. Read How to Cope with Deadlocks Source from Working around MySQL error "Deadlock found when trying to get lock; try restarting transaction" *All is well. I learn by answering your questions...*	[reply]
Re^2: fetchrow_hashref failed problem by dcunningham (Sexton) on Jul 21, 2015 at 07:07 UTC
Thank you, but the deadlock is not the problem. It's the fetchrow_hashref error following the execute.	[reply]


Syntactic Confectionery Delight
	PerlMonks