News for hackers. Stuff that matters.
Re:Betrayed by LinkedIn by narad on Friday January 11, 2013 @07:57AM (#5042448)
I get this drupal error.

-- PDOException: SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction: DELETE FROM {semaphore} WHERE (name = :db_condition_placeholder_0) AND (value = :db_condition_placeholder_1) AND (expire <= :db_condition_placeholder_2) ; Array ( [:db_condition_placeholder_0] => variable_init [:db_condition_placeholder_1] => 112720946350f00b3f105ad8.99608950 [:db_condition_placeholder_2] => 1357908800.0644 ) in lock_may_be_available() (line 181 of /export/content/data/dlc/shared/www/developer/includes/lock.inc). --

Why would somebody spit the SQL exceptions on the browser instead of the log file?

Re:Betrayed by LinkedIn by notzach on Friday January 11, 2013 @08:09AM (#5042493)
Clearly they don't understand how to configure drupal.
Re:Betrayed by LinkedIn by ahi on Friday January 11, 2013 @09:21AM (#5042745)
It's a big club.
Re:Betrayed by LinkedIn by RyanMcGreal on Friday January 11, 2013 @08:38AM (#5042578)
Why would the code to view a discussion thread be so cumbersome in the first place?
Re:Betrayed by LinkedIn by ssharp on Friday January 11, 2013 @09:17AM (#5042726)
Because it's Drupal.
Re:Betrayed by LinkedIn by citricsquid on Friday January 11, 2013 @08:12AM (#5042500)
Re:Betrayed by LinkedIn by n1c on Friday January 11, 2013 @09:18AM (#5042736)
From what I can tell the currently cached copy doesn't have the post in question.
Re:Betrayed by LinkedIn by Mahn on Friday January 11, 2013 @09:14AM (#5042714)
Offtopic, but drupal stores locks in a DB? That looks highly inefficient.
Re:Betrayed by LinkedIn by jarman on Friday January 11, 2013 @09:37AM (#5042809)
Because it's available everywhere, including shared hosting. IIRC it can be reconfigured to other storage mechanism