The Geo field module is doing lots of queries against a table that hasn't been created in the case of a 1-location-per-node field. In many cases the separate table (for the geo field) is not created, and the information is kept in the main content_type_XXX table.

* user warning: Table 'leslie_fruitandwine.content_field_listing_location' doesn't exist query: DELETE FROM content_field_listing_location WHERE vid = 34 in /home/leslie/public_html/sites/all/modules/contrib/geo/modules/geo_field/geo_field.module on line 225.
* warning: Invalid argument supplied for foreach() in /home/leslie/public_html/sites/all/modules/contrib/geo/modules/geo_field/geo_field.module on line 234.
* user warning: Table 'leslie_fruitandwine.content_field_listing_location' doesn't exist query: INSERT INTO content_field_listing_location () VALUES () in /home/leslie/public_html/sites/all/modules/contrib/geo/modules/geo_field/geo_field.module on line 250.
* user warning: Table 'leslie_fruitandwine.content_field_listing_location' doesn't exist query: SELECT SRID(field_listing_location_geo) as field_listing_location_srid, AsBinary(field_listing_location_geo) AS field_listing_location_wkb, AsBinary(Envelope(field_listing_location_geo)) AS field_listing_location_bbox, AsBinary(Centroid(field_listing_location_geo)) AS field_listing_location_centroid, delta FROM content_field_listing_location WHERE vid = 34 in /home/leslie/public_html/sites/all/modules/contrib/geo/modules/geo_field/geo_field.module on line 161.

Comments

allie micka’s picture

allie micka
she/her
commented
Status: Active » Postponed (maintainer needs more info)

"The Geo field module is doing lots of queries against a table that hasn't been created in the case of a 1-location-per-node field. In many cases the separate table (for the geo field) is not created, and the information is kept in the main content_type_XXX table."

That should never happen. See the discussion/details at http://drupal.org/node/388048 for the rationale on why there's always a per-field table. Can you explain how you came upon one of these "many cases"?

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

Thanks for your speedy response!

I think I know what's going on now... The rearrangement of the schema doesn't happen until the second page submit on configuring a geo field.

I just recreated this easily with this sequence:

1. Create a content type
2. Activate the geo, geo_field, gmap_geo modules
3. Add a geo field to my contact type. Field type: Geospatial data, widget=Gmap picker

At this point I looked in the database and saw three fields created in the content_type_xxx table: field_listing_location_geo, field_listing_location_lat, field_listing_location_lon.

4. Click "save field settings" on the field settings page

At this point, the database is rearranged with the items in content_field_xxx

So I guess it's happening correctly in the end, but I suspect that you'll see lots more of these, because many people forget to click the submit button on that second (field settings) page. And I doubt that it should be required that they do so.

Thanks for your effort maintaining the module! It's going to be a great new alternative. I'm looking forward to trying out other features of it.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Postponed (maintainer needs more info) » Closed (works as designed)

I think it is required to click that second submit. It may be troublesome, but I believe it is required by cck.