MySQL error:

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', 'Duplicate entry 'relativity_common_child_content-asset_content-as' for key 1\nquery: INSERT INTO variable (name, value) VALUES ('relativity_common_child_content-asset_content-asset', 'a:0:{}') in /hsphere/local/home/kumapage/dev.ludolab.org/includes/database.mysql.inc on line 120.', 2, '', 'http://dev.ludolab.org/admin/settings/relativity/advanced', 'http://dev.ludolab.org/admin/settings/relativity/advanced', '165.189.87.131', 1154579689) in /hsphere/local/home/kumapage/dev.ludolab.org/includes/database.mysql.inc on line 120

Comments

darius’s picture

I think it's the length of the variable name... (see issue http://drupal.org/node/62673) The solution is to modify the length of the "name" attribute in the table "variable" to, e.g., 256 (from 48). Let us know if that solves the problem.

Darius

darius’s picture

Status: Active » Fixed

Reopen if necessary.

Anonymous’s picture

Status: Fixed » Closed (fixed)
oprior’s picture

I am having a similar problem, where when I try to save display settings get several of the following errors spit out at me:

* user warning: Duplicate entry 'relativity_render_content_qc_flooring_content_qc' for key 1 query: INSERT INTO variable (name, value) VALUES ('relativity_render_content_qc_flooring_content_qc_flooring_colour', 's:5:\"title\";') in /home/oprior/drupal/includes/database.mysql.inc on line 121.

This only happens when I have a relationship set between parent and child cck nodes and they both have content.

I installed the latest version of Relativity that was uploaded today, but didn't fix my problem.

Can anyone shed some light on this? Maybe I'm doing something wrong...

Thanks,
Owen

darius’s picture

You'd have to modify the variable table on your own, since this is not a Node Relativity issue. Follow the links above.

John Bryan’s picture

I disagree about it not being a Node Relativity issue. The variable names are fine before the Node Relativity adds it's prefix.

As per my post http://drupal.org/node/290233 (thank you for responding to it) I suggest that storing Node Relativity data in it's own table should avoid variable length truncation.

As an intermediate meassure even changing Node Relativity's variable name prefixes, such as "relativity_child_ord_" to "rco_" would drastically reduce truncation instances. But a proper approach would be to have it's own table.

Sorry I only have time to stir and not to actually help with coding.

Regards

John Bryan