Hi Frans,

Collections are really simple and easy, it will be more helpful to have a method which will convert a collection to a DataTable. Just a thought.

Thanks.

You can load a collection as a datatable. GetMultiAsDataTable() is your friend (method of the entitycollections in selfservicing, static/shared).

If you need more overloads, let me know.

How about for the adaptor model. There is no getmultiasdatatable. Is there something similar.

Thanks

erichar11 wrote:

How about for the adaptor model. There is no getmultiasdatatable. Is there something similar.

No there isn't in the adapter model. I'll add that.

Hi Frans just found a need for the GetMultiAsDataTable() feature in the adapter model this morning has it been implemented yet?

Cheers

It turned out, there is already a feature for that FetchTypedList . Just do something like this:

CustomerEntity c = new CustomerEntity(); DataTable customers = new DataTable(); DataAccessAdapter adapter = new DataAccessAdapter(); adapter.FetchTypedList(c.Fields, customers, null);

If you want to filter, then pass a RelationPredicateBucket object instead of null

I just regen the DAL - There is no GetMultiAsDatatable in my Selfserv collections?

What version of LLBLGen is that in - I use 1.0.2003 Final April 30?

I must be missing something.

EmployeesCollection Employees = new EmployeesCollection();
Employees.??????????

Only have the following:

Employees.GetMulti Employees.GetMultiManyToManyUsingCustomersEntitiesForOrders Employees.GetMultiManyToManyUsingShipViaShippersEntitiesForOrders Employees.GetMultiManyToManyUsingTerritoriesEntitiesForEmployeeTerritories Employees.GetMultiManyToOne

I am doing an example on how to implement a BL with LLBLGen - using Northwind database. - Had a few requests. - Not enough hours in a day!

Still can't find it.

Downloaded the latest Tempates & Tasperformers for SQLServer and C# (Templates_SqlServer_04302004.zip, Taskperformers_SD_04302004.zip) - Just incase i was missing an update - GetMultiAsDatatable does not exist in the templates?

Am i going MAD? - Must be missing something else...

Found it! - knew i saw it before.

The Key =

It's a static method,

Not like

EmployeesCollection Employees = new EmployeesCollection();
Employees.GetMultiAsDatatable

but like

EmployeesCollection.GetMultiAsDatatable

Is it possible to return a DataReader?

Is DataTables used internally in the collections?

I have heard rumours that DataTables are very memmory hungry - wont it be better then to rather use a datareader?

wayne wrote:

Is it possible to return a DataReader?

Is DataTables used internally in the collections?

I have heard rumours that DataTables are very memmory hungry - wont it be better then to rather use a datareader?

Collections are filled with objects which are filled by a datareader It is not possible to return a datareader, nor do I think that's very wise, as the datareader is a very low level object.

Collections are filled with objects which are filled by a datareader

Are theses objects created and filled as they are resquested? - like load on demand? Or are they just all created when the collection getmulti is called?

The reason that i am asking is because we have noticed that our collections are very memory hungry. A load on demand for collection's would be nice.

Edit - yep sometimes our collection retreives every record - BAD BAD I know.

wayne wrote:

Collections are filled with objects which are filled by a datareader

Are theses objects created and filled as they are resquested? - like load on demand? Or are they just all created when the collection getmulti is called?

The reason that i am asking is because we have noticed that our collections are very memory hungry. A load on demand for collection's would be nice.

When you request 100 entities from the db, you will get 100 objects: each row read by the datareader will end up as an entity object.

So if you don't need all objects, specify a tighter filter to fetch less.

wayne wrote:

I have heard rumours that DataTables are very memmory hungry - wont it be better then to rather use a datareader?

DataReaders leave the connection open as well until it's destroyed, and they're forward only i.e. they're not very portable.