The error I get is:
user warning: Unknown column 'lid' in 'where clause' query: DELETE FROM location WHERE lid = 9 in /var/www/drupal_5.1_20070214/html/includes/database.mysqli.inc on line 151.
My "location" table in the database has the following structure:
mysql> desc location;
+--------------+---------------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+--------------+---------------------+------+-----+---------+-------+
| eid | int(10) unsigned | NO | PRI | 0 | |
| type | varchar(6) | NO | PRI | NULL | |
| name | varchar(255) | YES | | NULL | |
| street | varchar(255) | YES | | NULL | |
| additional | varchar(255) | YES | | NULL | |
| city | varchar(255) | YES | | NULL | |
| province | varchar(16) | YES | | NULL | |
| postal_code | varchar(16) | YES | | NULL | |
| country | char(2) | YES | | NULL | |
| latitude | decimal(10,6) | YES | | NULL | |
| longitude | decimal(10,6) | YES | | NULL | |
| source | tinyint(4) | YES | | 0 | |
+--------------+---------------------+------+----+---------+-------+
Comments
Comment #1
geodaniel commentedHave you run update.php since updating? If you have, this could be related to http://drupal.org/node/116599
Comment #2
stella commentedYep I've run update.php since getting this error. I'm not sure if it's related to issue http://drupal.org/node/116599 but I do have the Views module enabled, ditto with GMap, GMap Location, GMap Macro Builder, GMap Views Integration, Location Views and KML.
Cheers,
Stella
Comment #3
stella commentedI've dropped my location table and recreated it using the sql provided in the 116599 issue. Everything is working fine now.
Stella
Comment #4
geodaniel commentedSounds like a bug in the upgrade process then. Do you remember seeing any errors when you ran update.php previously?
Comment #5
stella commentednot with update.php. The only other problem I had with the location module was in relation to php5 and array_merge(), now fixed, but that's unconnected with the database schema.
Anyway I'm happy for this to be closed off.
Thanks,
Stella
Comment #6
mfredrickson commentedI'm seeing this error on a fresh D5 install with location.
I think the problem is actually with gmap_location. The install file for that module has this in it:
As you can see, it creates it's own location table. If it is enabled before location, all heck breaks loose.
I'm going to go file an issue there. Why are is gmap_location creating it's own location table? I'd guess this is a holdover from when gmap_location was a fork of location.
Comment #7
niklp commentedI'll close this, because it's been addressed in another issue that's been patched and committed.