How much ORMish is lightspeed 5

I am coming from EF6 at the moment and I do not feel spoiled by its features.

There are some pain points where I feel thrown back to sql times when it comes to certain scenarios.

This is what I miss from EF6:

1) Lazy loading of properties without the EF splitting table...

2) Do an update on an Entity without updating all fields, that means the fields which are not updated must keep the original values.

3) Code First index constraint on multiple fields generation

4) Something like context.Customers.Delete(c => c.CreationDate > mydate && ); context.SaveChanges(); I do not want to retrieve all the customers just to delete them. Just know I do not know the ids of the customers. This is a deletion on common fields.

5) Also I would like to update something strongly typed in lambda fashion.

Thank you for an answer :)

1. We support lazy loaded properties via our named aggregates. If an aggregate is specified for an entity property that property will be lazy loaded (on access) unless the aggregate has been specified for the query. There is some more detail about this in the docs here: http://www.mindscapehq.com/documentation/lightspeed/Performance-and-Tuning/Understanding-Named-Aggregates and on this blog post here: http://www.mindscapehq.com/blog/index.php/2011/01/19/controlling-lightspeed-entity-loading-with-named-aggregates/

2. If I understand correctly you are wanting to avoid sending down values for fields which have not changed in the entity avoiding concurrency related issues? If so we have two ways of handling this - via use of the LockVersion flag on an entity which requires a separate field and performs a concurrency check prior to update and then only updates fields which have changed, or when the entity has the UnversionedPartialUpdate attribute applied we will only send down an update statement containing the tracked changes and not all fields. There is some more info in the docs about both of these here: http://www.mindscapehq.com/documentation/lightspeed/Implementing-Storage-Policies-with-LightSpeed/Concurrent-Editing and here: http://www.mindscapehq.com/documentation/lightspeed/Implementing-Storage-Policies-with-LightSpeed/Change-Tracking

3. Sorry Im not sure what you mean, are you able to point me at something to help clarify? :)

4. To cover this you will want to use a remove by query, we have an overload on UnitOfWork.Remove which takes in a query object specifically for this scenario. There is a LINQ extension method named Remove available under the Mindscape.LightSpeed.Linq namespace that will handle this also. There is some more info in the docs here: http://www.mindscapehq.com/documentation/lightspeed/Performance-and-Tuning/Bulk-Updates-and-Deletes

5. Similar to the above, we support an Update by query, taking in a hash of the property value pairs to update with. This is also detailed via the above doc link. We dont have a lambda based option for handling this however and the queries need to be constructed using our specification API.

Jeremy

Thanks for all the info.

about 3) Can I configure a unique constraint on multiple fields with Code First approach? (Assuming you have Code First...)