What are the benefits I can get by upgrading LLBLGen V 2.0 to V 2.6 ?

I am more looking in to Performance improvement and better SQL statements including Derived Table Definitions and also is it any better or different way of doing Concurrency predicate with V 2.6?

concurrency predicates: no changes, as it worked properly. performance: many improvements, especially in the memory consumption area and also in fetching entities. Also little tweaks like not emitting 'TOP 1' with scalar queries, not emitting DISTINCT if not necessary etc. v2.6 also has derived table support which allows you to formulate queries which weren't possible before (including using linq).

Is there any way I can do a Batch Update / Insert with the new version? I mean sending as a list of entity objects to update / insert.

Amith wrote:

Is there any way I can do a Batch Update / Insert with the new version? I mean sending as a list of entity objects to update / insert.

using a UnitOfWork object you mean? That can be done for a long time already (also in 2.0). Just add objects for persistence to the unit of work object, then commit it to do everything in 1 go (deletes as well).

Batching of INSERT or UPDATE SQL statements isn't supported.

So I'm not entirely sure what you mean, could you give an example?

Otis wrote:

Amith wrote:

Is there any way I can do a Batch Update / Insert with the new version? I mean sending as a list of entity objects to update / insert.

using a UnitOfWork object you mean? That can be done for a long time already (also in 2.0). Just add objects for persistence to the unit of work object, then commit it to do everything in 1 go (deletes as well).

Batching of INSERT or UPDATE SQL statements isn't supported.

So I'm not entirely sure what you mean, could you give an example?

I am trying to send a list of objects to persist instead of sending one by one. I didn't try UnitOfWork. I will have a look at it. Or is there anything better?

Amith wrote:

Otis wrote:

Amith wrote:

Is there any way I can do a Batch Update / Insert with the new version? I mean sending as a list of entity objects to update / insert.

using a UnitOfWork object you mean? That can be done for a long time already (also in 2.0). Just add objects for persistence to the unit of work object, then commit it to do everything in 1 go (deletes as well).

Batching of INSERT or UPDATE SQL statements isn't supported.

So I'm not entirely sure what you mean, could you give an example?

I am trying to send a list of objects to persist instead of sending one by one. I didn't try UnitOfWork. I will have a look at it. Or is there anything better?

It's what you need. You can also just save an entity collection btw, that also will work in your situation.