currently whilst developing on Linq to NHibernate a lot of problems have
shown up. The criteria api of NHibernate does not provide all features
needed to fully implement Linq2Nhib. Thus they want to abandon the use of
the criteria api and are working on a version that translates the query Linq
to a
very very nice! Now ALL my tests pass! Congratulations, I think this mapping
framework now starts to be mature. I'll continue to post articles in the
NHibernate FAQ blog and take it to the limits... :-))
On Tue, Aug 26, 2008 at 10:55 PM, James Gregory <[EMAIL PROTECTED]>wrote:
> Hey Gabriel,
> Th
plus I guess, if you want the quoting just put it in the table name or
something, eh?-d
On Wed, Aug 20, 2008 at 12:33 AM, Gabriel Schenker <[EMAIL PROTECTED]>wrote:
> I had issues with the ` auto quoting of NHibernate (in conjunction with
> SqLite IIRC)
>
>
> On Wed, Aug 20, 2008 at 1:47 AM, Dru
So I was going to follow up on this patch but I had some problems because
the ConnectedTester relies on SqlServer2005. I decided to see how quickly I
could get it swapped over to using in-memory Sqlite, and to my dismay it was
not particularly straightforward. It took a while to hunt down, but it t
Hey Gabriel,
This completely fell off my radar just before I went away, sorry about that.
I've committed a fix that at the very least makes your test pass! Hopefully
it should let you carry on.
On Tue, Aug 19, 2008 at 8:08 AM, James Gregory <[EMAIL PROTECTED]>wrote:
> Thanks Gabriel, I'll take a
Hey Andy,
I was wondering if you have decided where to go with this code? I thought my
patch would be a good option if you don't want to engage in a larger
refactoring.
Paul Batum
On Sun, Aug 17, 2008 at 6:20 PM, Paul Batum <[EMAIL PROTECTED]> wrote:
> Hey Andy,
>
> I decided to tackle your pro
Hi Dan
Sorry for the slow delay but I've been answering you by mobile phone as I've
been away from my pc most of the weekend. Does anything need changing to
make AutoMapper work for you in your situation.
Cheers
Andy
On Mon, Aug 25, 2008 at 8:53 AM, Andrew Stewart <
[EMAIL PROTECTED]> wrote:
>
Hi Derik
I think the thing to remember is linq isn't linq to sql or the entity
framework(I'm sure you realise this but just thought I'd restate it)
and as a query language personally I think it rather good. I tend to prefer
linq as lambda expressions rather than :
var qry = from product in produc
I noticed that the ConnectedTester.MappingTest1 test was failing
because the location property wasn't included in the mapping. I
uploaded a patch to fix this to the group's file section.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to t
It's currently part of NHContrib, but hasn't been updated to work
against 2.0 GA yet. I'm not sure if/when this will happen.
I believe the intention is NH.Linq to become part of the official
distribution for the 2.1 release, but I'm not sure when that will be
happening.
On Aug 26, 10:57 am, Deri
Or use a "Nested Closure" in the FI to have a full end around for all little
one off customizations:
.OverrideMapping(Action< IProperty > action) that returns PropertyMap
or use an anonymous class like the MVC for the name/value properties
Jeremy D. Miller
The Shade Tree Developer
[EMAIL PRO
IMHO, -1 on the anonymous class
On Tue, Aug 26, 2008 at 9:49 AM, Jeremy D. Miller
<[EMAIL PROTECTED]>wrote:
> Or use a "Nested Closure" in the FI to have a full end around for all
> little one off customizations:
>
> .OverrideMapping(Action< IProperty > action) that returns PropertyMap
>
> or us
I thought NH.Linq was dead. all of the info from google and ayende's
posts go to a dead URL (blogs.magiconsoftware.com). looks like it's
still up and running, though, as part of NHContrib. I'll have to do a
bit of R&D on this.
the next question is: would NH.Linq obviate the need for making NH's
c
Derick, have you looked at NHibernate.Linq?
An early post from Ayende on it (I'm sure you will find more if you google):
http://www.ayende.com/Blog/archive/2007/03/16/Linq-for-NHibernate.aspx
The source:
http://nhcontrib.svn.sourceforge.net/viewvc/nhcontrib/trunk/src/NHibernate.Linq/
On Tue, Aug
It doesn't use reflection in the query execution - only in the
creation. it calls down to the standard NHibernate Criteria/Criterion
API's after retrieving the property name via reflection. the minor
performance hit of using reflection in the query creation is far
outweighed by the benefits of com
Thanks!
This worked:
Map(x => x.Number).AsReadOnly().SetAttribute("generated", "always");
On Tue, Aug 26, 2008 at 1:29 PM, James Gregory <[EMAIL PROTECTED]>wrote:
> You should be able to get your insert="false" by using AsReadOnly. The
> generated attribute isn't supported yet, so you'll have t
You should be able to get your insert="false" by using AsReadOnly. The
generated attribute isn't supported yet, so you'll have to continue to use
the SetAttribute for that.
Regarding the void for SetAttribute, that is a bit of a pain. it won't be as
simple as just returning IHasAttributes, because
Hi everyone
Just faced this requirement and don't know yet how to do it in the
simplest way.
The mapping that I'd like to map fluently:
This can be easily solved if it would be possible to add two
attributes to PropertyMap. But PropertyMap.SetAttribute() returns
void, so it cannot be chained f
18 matches
Mail list logo
