For starters, having the code generated is a big plus. The thought of having to hand code collections is not appealing. I do enough monkey work it seems.
You definitely make a good point about the updating, however, I'm going to have to do the same thing with my own collections anyhow. This is a case where I'm really not using the tool as it was designed to be used, and I understand that. I'm just seeing if there's a way I can use it to save time and effort.
Somehow I don't think we're going to get Frans to add that level of support for stored procs. Although, for me, it would be nice in this particular situation.
I'm still sitting here trying to figure out if I want to use LLBLGen for this product or not.
Thanks for the response.
Fishy wrote:
I use DataAdapter and I use the Entities within my PL. I bind the EntityCollection to grids.
If the user changes information in the grid I simply call the dataadapter Save method against the EntityCollection (in the BL, of course) and my data base is updated.
The works very well.
I had once thought, hey it would be great to call a stored proc, create the EntityCollection and perform binding and updates. Of course the problem is I could not dynamically update with the dataadapter. I would have to go thru the EntityCollection, see what was updated, and then call a stored proc to perform the update.
So, what would the point be of creating the EntityCollection as opposed to using a DataTable?
Now, if Frans could make a change to map a stored proc, associate additional stored procs for doing updates and deletes and have a way to check for schema consistancy (optional, could trust the programmer/dba); that would be fantastic.