My reason for MySQL was that more people have it, and it comes with spatial extensions by default in 5.0.
nym On 2/1/06, Kevin Elliott <[EMAIL PROTECTED]> wrote: > It would probably make sense to mimic the ActiveRecord implementation of ORM > in Rails and be as db platform independant as possible, that way as many GIS > databases can be used. Probably no easy task, but wise to do. > > Maybe we can start shelling up a skeleton of GIS functionalities in > PostgreSQL, MySQL and Oracle that might be useful in Rails (and perhaps Ruby > in general), and maybe move the discussion offlist after that. > > Kevin > > ----- Original Message ----- > From: "Scott Davis" <[EMAIL PROTECTED]> > To: <[email protected]> > Cc: <[EMAIL PROTECTED]> > Sent: Wednesday, February 01, 2006 12:29 PM > Subject: Re: [Geowanking] Ruby On Rails Wanking > > > Any reason why you're not considering PostGIS to handle the geodata? > It's *way* more mature than the native MySQL stuff. > > http://wiki.rubyonrails.com/rails/pages/PostgreSQL > > So ActiveRecord/Postgres seems to be doable. Getting the PostGIS/OGC > data elements out seems to be the next hurdle. Java and C bindings > are native to the project. Maybe some SWIG magic to add ActiveRecord > support? Or as someone previously mentioned in this thread, there are > Ruby bindings for ogr2ogr out there in the wild. > > My $0.02, > s > > Scott Davis > [EMAIL PROTECTED] > > > > On Feb 1, 2006, at 1:03 PM, Tom Longson (nym) wrote: > > > No team, nothing found yet. I put out a call on the Ruby on Rails list. > > > > Would be interested in getting this knocked out at least for POINT. > > > > The syntax is dead simple imo. > > > > CREATE TABLE narf (egad POINT); > > INSERT INTO narf (GeomFromText('POINT(1 1)')); > > SELECT x(egad), y(egad) FROM narf; > > > > (I think that's it, I didn't double check the syntax) > > > > nym > > > > On 2/1/06, Kevin Elliott <[EMAIL PROTECTED]> wrote: > >>>> wondering if any of you wankers were playing with it. It doesn't seem > >>> > >>> /me waves > >> > >> At the cost of sounding cliché, me too! > >> > >>>> like it has support for MySQL's spatial datatypes/functions > >>>> unfortunately. I was hoping to be able to throw up a geo app quickly > >>>> yet avoid the amaturish thing of storing x and y coordinates in double > >>> > >>> It's often quicker that way (database wise). > >>> > >>>> fields. I'm thinking about trying to extend rails to support these > >>>> datatypes but wanted to see if anyone was doing similar work first. > >>> > >>> Not that I know of, interesting idea. Ping the Rails list? > >> > >> As a relative new Rails developer, but thoroughly assimilated, I have > >> been > >> curious about this too. It might be something fairly easy to add if > >> you're > >> very familiar with the geospatial features in MySQL. I'm still looking > >> at > >> the geo functions in MySQL, and haven't had a chance to interface with > >> it > >> directly yet, but I'm interested. Perhaps we can team up and chunk out > >> some > >> code. Have you put together a small team or found something existing > >> yet? > >> > >> Kevin > >> > >> _______________________________________________ > >> Geowanking mailing list > >> [email protected] > >> http://lists.burri.to/mailman/listinfo/geowanking > >> > > _______________________________________________ > > Geowanking mailing list > > [email protected] > > http://lists.burri.to/mailman/listinfo/geowanking > > _______________________________________________ > Geowanking mailing list > [email protected] > http://lists.burri.to/mailman/listinfo/geowanking > > _______________________________________________ > Geowanking mailing list > [email protected] > http://lists.burri.to/mailman/listinfo/geowanking > _______________________________________________ Geowanking mailing list [email protected] http://lists.burri.to/mailman/listinfo/geowanking
