So regardless of the outcome of moving into the trunk or not, I do want to actively maintain Spatial. How do I get started with this?
On Sun, Apr 25, 2010 at 9:34 AM, David Pfeffer <[email protected]> wrote: > I'll go ahead and make a ticket. Should I put this under the core or under > the Spatial project? > > -David > > > On Sun, Apr 25, 2010 at 2:49 AM, Fabio Maulo <[email protected]> wrote: > >> NH2.1.2 (last released) has only 54993 downloads. >> Create a new JIRA ticket to include Spatial in core, publicize your ticket >> every where and invite people to vote for it... we will know when the time >> become soon. >> >> >> On Sun, Apr 25, 2010 at 2:47 AM, Gareth <[email protected]> wrote: >> >>> I agree with David on this...but....I also agree with Fabio. As long >>> as spatial is not ubiquitous (ie: only supported by a few databases) >>> then it should remain outside of core. However, once *most* databases >>> have spatial support then data-types like geometry and geography >>> become first-class citizens like varchar and int. At that point in >>> time I believe that NH Spatial should move into core. The question is, >>> how do we decide when that time is? >>> >>> On Apr 25, 5:59 am, David Pfeffer <[email protected]> wrote: >>> > Thanks for the link. That project unfortunately is a LINQ to Objects >>> > implementation of GIS querying, however. What's really lacking is >>> support >>> > for querying said spatial data from a database, such as in a where >>> clause. >>> > These queries rely on the database's native spatial indexes, and are >>> > substantially faster than in-memory manipulation of geospatial data. >>> > >>> > >>> > >>> > >>> > >>> > On Sat, Apr 24, 2010 at 1:53 PM, Fabio Maulo <[email protected]> >>> wrote: >>> > > On Sat, Apr 24, 2010 at 2:37 PM, David Pfeffer <[email protected] >>> >wrote: >>> > >>> > >> IMO, the NHibernate core should support everything that the >>> database >>> > >> engine supports, right out of the box. If the consensus is that this >>> isn't a >>> > >> good policy, then I'll go about extending the core with >>> extensibility points >>> > >> for Linq. (I don't think Spatial is going to go anywhere without >>> full Linq >>> > >> support.) >>> > >>> > >http://linqtogeo.codeplex.com/ >>> > >>> > > -- >>> > > Fabio Maulo >>> > >>> > -- >>> > Subscription settings: >>> http://groups.google.com/group/nhibernate-development/subscribe?hl=en >>> >> >> >> >> -- >> Fabio Maulo >> >> >
