Bugs / Issues

First post was here:

http://www.mindscapehq.com/forums/Thread.aspx?ThreadID=4869

1) In addition to this, I've noticed that when you add a new entity, it doesn't default the identity to the type defined in the policy.

E.G, my policy says identity generation is GuidComb, however it defaults the type to Int32.

2) There's no option in the properties (that I can find) that allows you to define a relationship's Eager/Lazy load as 'ExtraLazyLoad'

3) If you give the Model Designer a ConnectionString, and then go to the 'getting started' in order to generate the starting point for the sessionfactory, I think you should make the connection string a verbatim string literal by default.

I'll add to this if I find anything else.

Thanks for the feedback.  I've added some additional validation and filtering so that the wizard will now offer only the appropriate default identity generators for the default identity type (if there is one), and I've updated the Get Started screen to use a verbatim string literal (also added a fix for connection strings that contained quotes).  These will be included in the next update.

We don't currently support extra-lazy loading as it seems a very niche use case, but we'd welcome feedback on how important this is -- thanks for drawing our attention to this!

Extra-Lazy loading is good for some scenarios like...

Given you have an Order with OrderItems collection.

If you were to do:

//Get Order from DB by ID.

var numberOfOrderItems = order.OrderItems.Count();

This would cause the entire collection to be loaded from the database.

When you turn on Extra-Lazy, rather than selecting the entire collection, it would re-evealuate what you're trying to do first, in this case, count the number of items. So it would do:

SELECT COUNT(*) FROM OrderItem WHERE OrderId = 5

Tho, it's like a little hidden feature of NH.

Could you include support for defining the default access to the identity property.

It would be nice if the policy allowed me to specify the setter of the id to be protected set:

public virtual Guid Id { get; protected set; }

Support for composite Ids is awesome by the way!

Thanks for the feedback. I've added a Visibility option to the Default Identity Type policy as requested; there's also a new visibility of PublicGetProtectedSet, which you can apply to any property (as well as selecting it in the Default Identity Type policy). These will be in the next update.

I've logged a feature request for extra-lazy loading but I can't commit to a date; is this a major thing for you, or a 'nice to have'?

It's a 'nice to have' thing. At the moment I'm just trying to break the designer and find things that are missing or could be better. So no hurry. :)