Hi, I was messing around w/ views and everything just basically went downhill. Here is what I got back from my host support because I wasn't able to 1. access the site and 2. access mysql.
Support response: 2006/10/29 21:18
I does look like a locked query is the problem. Here is a sample of your running processes:
| 5531539 | layout | 10.1.3.18:55236 | layout_db | Query | 39824 | statistics | SELECT node.nid, node.title AS node_title, node.changed AS nod
e_changed, node.created AS node_create |
| 5535645 | layout | 10.1.3.18:56296 | layout_db | Query | 39728 | statistics | SELECT node.nid, node.title AS node_title, node.changed AS nod
e_changed, node.created AS node_create |
| 5538730 | layout | 10.1.3.18:39476 | layout_db | Query | 39649 | Locked | UPDATE users SET access = 1162144907 WHERE uid = 1
|
| 5539249 | layout | 10.1.3.18:39601 | layout_db | Query | 39636 | Locked | SELECT u.*, s.* FROM users u INNER JOIN sessions s ON u.uid =
s.uid WHERE s.sid = 'b681e5077cb033ff3 |
| 5541983 | layout | 10.1.3.18:40415 | layout_db | Query | 39566 | Locked | SELECT u.*, s.* FROM users u INNER JOIN sessions s ON u.uid =
s.uid WHERE s.sid = 'b358a20b3bff07aa1 |
| 5544138 | layout | 10.1.3.18:41047 | layout_db | Query | 39512 | Locked | SELECT u.*, s.* FROM users u INNER JOIN sessions s ON u.uid =
s.uid WHERE s.sid = 'b358a20b3bff07aa1 |
| 5546123 | layout | 10.1.3.18:41538 | layout_db | Query | 39463 | Locked | SELECT u.*, s.* FROM users u INNER JOIN sessions s ON u.uid =
I am looking for a Drupal database neutral alternative to mysql_insert_id that has good performance. I looked at db_next_id but on MySQL it involves four queries and a database lock/unlock.
There were various discussions in these forums about alternatives in particular:
I don't see a Drupal function comparable to mysql_insert_id. Obviously using the command would mean PostgreSQL wouldn't work (would it?)... so I'm curious if instead of using mysql_insert_id after an insert I should use db_next_id before the insert to store the next insert's id.
I'm part of a not-for-profit organization called Janaagraha based in Bangalore, India. We've just recently developed our website www.janaagraha.org using Drupal and hosted it on Siteground. We had outsourced the development of our Volunteer Management System to another company which developed it using core PHP. The Volunteer Management System used to work on our old website hosted on Yahoo! but has stopped working since we moved it to Siteground.
I just got this problem with my drupal site today. I have not made any changes or anything. It worked last night, but when iw oke up this morning i only get this error message: