When I go to do a full buddylist migration, I get a page full of "watchdog not locked" mysql errors. Here is one example:
Warning: Table 'watchdog' was not locked with LOCK TABLES query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (1, 'php', 'You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'LIKE user_relationships' at line 1\nquery: CREATE TEMPORARY TABLE user_relationship_migration LIKE user_relationships in /home/www/mysite.com/includes/database.mysql.inc on line 174.', 2, '', 'http://mysite.com/admin/user/relationships/migrate', 'http://mysite.com/admin/user/relationships/migrate', '73.12.87.2', 1242259791) in /home/www/mysite.com/includes/database.mysql.inc on line 174
--
MySQL 4.0.26
PHP 4.3.8
Comments
Comment #1
alex.k commentedDoesn't sound related to UR. You should, however, investigate the error watchdog was trying to report, i.e. error in 'create temporary table' SQL.
Comment #2
AppleBag commentedYa think it might be due to my MYSQL version being a bit old? What is the minimum MYSQL version required by the module?
Comment #3
alex.k commentedNot sure as this was written before I became maintainer. Please check the query and which parts may be unsupported. But yeah I'd upgrade to 5.x definitely.
Comment #4
stella commentedI get a similar error:
It seems to be triggered by a duplicate insert into the user_relationships table. I'm using mysql 5.0.x
Comment #5
plan9 commentedI have the same issue - it stops the migration taking place.
Comment #6
plan9 commentedI found that un-installing user relationships and installing the previous 5.x-1.0 release allowed me to successfully migrate from buddylist. After this I upgraded to the current user relations release.
You can get the old version here: http://ftp.drupal.org/files/projects/user_relationships-5.x-1.0.tar.gz
Hope this helps
Comment #7
berdirSorry for pinging the participants.
Now that Drupal 7 is out, there is no support for Drupal 5 and the corresponding modules anymore. Therefore, I'm closing all old issues which are still open.
I suggest you upgrade to Drupal 6 or 7 and figure out if you're feature is still needed or the bug still exists and open a new issue in that case.