Pretty much georuby will do the trick, but i'd really like to be able to define it in a model as say
property :boundary, Polygon and hook into auto_migrate! so that it issues the correct SELECT AddGeometryColumn(.......); I can't see an obviously hook point from within dm-types though. Like there is no primiative for this (I could use the wkt as a string but you completely loose GIST indexes etc then). Am I missing something? On Jan 13, 3:05 pm, Michael Klishin <[email protected]> wrote: > On 13.01.2009, at 17:58, heda wrote: > > > Anyone have any ideas on this? I was going to use GeoRuby as the main > > object and just write a dm-type to shunt between the database and it. > > It was a while I worked with postgis :) So, you want to say turn a > Ruby object into a GIS surface type? Does GeoRuby work for you ok? > Because if it is not perf critical, just use georuby, this is how some > types in dm-types work, through simple delegation: json, xml, bcrypt > hash, ipaddr. > > MK --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
