By amitbapat on

When upgrading from 4.6.5 to 4.7 I get an error: Unknown column 'access' in 'field list' query: UPDATE users SET access = 1147026055 WHERE uid = 1 inincludes/database. mysql.inc on line 120.

This error appears in the log 3 times.

details
Type php
Date Sunday, May 7, 2006 - 11:20
User admin
Location http://mysite.com/update.php?op=selection
Referrer http://mysite.com/update.php
Message Unknown column 'access' in 'field list' query: UPDATE users SET access = 1147026055 WHERE uid = 1 in /home/user/mysite.com/htdocs/includes/database.mysql.inc on line 120.
Severity error
Hostname 192.168.11.72

the site is still functional but my non-english text (devanagari characters which use UTF-8 is garbled).

I'm using CentOS 4.3, with apache 2.0.52, php 5.0.4, mysql 5.0.18.

Please help!

⋅ Categories: Drupal 4.7.x

Comments

alexmarkley’s picture

alexmarkley commented

I noticed the access entries too. I think it's safe to ignore those. (Correct me if I'm wrong?)

As for the character issues, I can't say much to those, but I'm pretty sure they're not related.

Alex Markley--
--A warehouse is just like any other house, except it turns EVIL under the light of a full moon.

Taran’s picture

Taran commented

Are probably a UTF8 issue. If you have a backup of your database that isn't garbled, you may want to upload that... if not, you might want to do find/replace. Basically, the character issue isn't as much of a Drupal problem as it is a MySQL issue. From what I've been reading (and I've been reading a LOT since this last upgrade), UTF8 should have been forced in the upgrade... but apparently wasn't. I had similar problems with Spanish characters, and ended up doing REPLACEs to fix them.

I do NOT know if this will work with Devanagari chars. If you do something like below: Back Up Your Database before.

The MySQL replace statement might look like:

UPDATE node_revisions SET body = REPLACE (
body,
"garbled chars",
"ungarbled chars");

Which fixes the body... then replace 'body' with 'teaser', and so forth. Again, this might not work and ALWAYS back up your database before doing things with it.

KnowProSE.com
OpenDepth.com