Which RDBMS are you talking about ? We are supporting various. On Sat, Apr 24, 2010 at 2:37 PM, David Pfeffer <[email protected]> wrote:
> You make a really good point. > > However, shouldn't the criteria also be database support? 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.) > > > On Sat, Apr 24, 2010 at 1:21 PM, Richard Brown (gmail) < > [email protected]> wrote: > >> Linq (like generics) started out as a separate project. However, Linq >> (again like generics) is built in to c#. >> >> Note, that's different to being a namespace in the .Net framework; >> generics and Linq are part of the core language syntax. I suspect >> everything else is game for being pluggable. (Unlike the core c# language >> which OSS can't, unfortunately, affect.) >> >> >> *From:* David Pfeffer <[email protected]> >> *Sent:* Saturday, April 24, 2010 5:31 PM >> *To:* [email protected] >> *Subject:* Re: [nhibernate-development] NHibernate Spatial Development >> >> I totally understand and support this philosophy. What I'm looking for is >> justification to designate NHibernate Spatial as a separate project. >> Consider the other NHibernate Contrib projects: >> >> NHibernate Linq - moved into NH core! >> With the exception of NHibernate Linq, each one of these contrib projects >> are easily separable from NHibernate and provide an ancillary ability. That >> isn't the case for Linq, and the new Linq provider is in the core now! >> >> > -- Fabio Maulo -- Subscription settings: http://groups.google.com/group/nhibernate-development/subscribe?hl=en
