User: vauxia Branch: HEAD Date: Fri, 08 Aug 2008 04:20:33 +0000 Modified files: /modules/geo/db mysql_spatial.inc postgis.inc /modules/geo geo.module /modules/geo/modules/geo_field geo_field.module Log message: Restored field storage functionality to geo_field and updated to CCK 6.x spec. Rather than carefully maintaing and tracking our own tables, I'm piggybacking on the existing CCK table storage: - All fields are forced to 'multiple' storage - hook_field('database columns') returns extra fields such as lat, lon, etc. - After CCK creates a valid field storage table, we sneak in and drop/replace its geo field with a valid geometry table definition. I still need to manhandle the save operations because I couldn't get around query substitution issues. However, the table structure and operations behave pretty much like what you'd expect from CCK. This minimizes code duplication and allows me to fantasize about defining datatypes via the schema API, which would obviate all of this mincing about. Links: http://cvs.drupal.org/diff.php?path=contributions/modules/geo/db/mysql_spati... http://cvs.drupal.org/diff.php?path=contributions/modules/geo/db/postgis.inc... http://cvs.drupal.org/diff.php?path=contributions/modules/geo/geo.module&old... http://cvs.drupal.org/diff.php?path=contributions/modules/geo/modules/geo_fi...