Bug with Saving items loaded with Aggregates (EagerLoad)

I am using the latest 041109 Nightly build.

I have a Config Object and a child collection called ConfigsToProductSize

The Relationship is a one to many.

I have set a Collection Aggregate and then I load the Config object using FindOne<Config> 

var query = new Query() {
 AggregateName = "Populated",
 Identifier = configId,
 IncludeDeleted = false
};
var retVal = uow.FindOne<Config>(query);

I make a change to one of the ConfigsToProductSize objects and the EntityState does turn to Modified but when you save changes, nothing is executed against the DB.

I then went and looked on the UOW collection for ConfigsToProductSize and the item state was Normal.

It appears that an Eager loaded child object does not get placed into the UOW Cache.

The reason I say this is because I then did the following.

I then tried to load the Config up using this syntax

uow.Configs.FirstOrDefault(c => c.Id == configId && c.IsDisabled == false);

I then changed a ConfigsToProductSize (you can see it loading)

I then look at the uow collection and the item state is Modified just like the object I just modified.

When I save, it the item is saved correctly.

I obviously tried the code without looking at the collection, so it was not a fluke, the item does save every single time if the Aggregate is not used.

I will use non aggregate loads until this bug is fixed. If you need any additional information, feel free to contact me.

Joe Feser

PS I am getting an HResult Error in the designer when I right click on an entity. I may need to reboot but give it a try.

Hi Joe,

Just a quick note about getting the HResult error. Could you please try uninstalling and re-installing LightSpeed? You'll need to do this via the add/remove programs control panel applet.

A few weeks back I altered the installation process to automatically uninstall previous versions because it was a pain that you always had to go to thecontrol panel. The side effect of this was that some users wouldn't uninstall the previous version and the LightSpeed designer ends up a bit confused with respect to the VS integration. I've only seen this once myself and it manifested itself in the same thing you're seeing with the HResult problem.

If you could let me know if that fixes this specific issue I would be very appreciative :-)

We'll look into the actual issue you raised on Tuesday (the Monday is a public holiday for Easter here).

Kind regards,

John-Daniel Trask

John, 

A full uninstall and reinstall did work. I am back to the 041109 version from 033009.

Thanks for answering on a Saturday afternoon.

As long as we can resolve the other issue in the next week or so I am good. I am on a local W2k3R2 box so the extra queries are not an issue at this time.

Do you think you have enough info to reproduce the issue or do I need to create a sample project?

In about 8 hours time I was able to convert an entire EF project with 40 or so tables to Lightspeed 2.2 (033009). So far I am lovin it. I got a good laugh after being confused for a few minutes on how you name an entity for a table called "LogoData", it became LogoDatum.

Thanks,

Joe Feser

Hi Joe,

I have tried to reproduce this using our test suite but I am seeing child object updates being sent to the database just as one would expect.

Would it be possible for you to prepare a simple project that demonstrates the problem?  We would need:

* A complete runnable project containing:
  * The C# or VB entity classes (don't need the .lsmodel)
  * A piece of code that performs the query and save operation that isn't working correctly (ideally as a console application, NUnit test or one-button WinForms app)
* The SQL CREATE TABLE scripts for the tables involved

You can attach a zip file via the Options tab, or email it to me on ivan @ the obvious domain name (please strip out all binaries first).  Thanks!

That is a bummer that it was not reproducable.

Give me an hour.

Can I give you a sql mdb file since it will be easier to load it with data?

The zip file should still be under a meg.

Sql 2005 is my database.

You guys should give kudos to John-Daniel, he has been very helpful, the boss would be very happy. :)

Joe

Yep, a MDF file would be fine.

Either I have some crazy stuff going on in my model or there is one heck of a state bug.

I tried creating a very simple model but I was not able to reproduce the issue.

I am still going one object at a time until I track down the root cause. I can't send you the 20 meg db that it is reproducable in.

It may take a day or so for me to find the exact steps needed in a simple model.

I will get back to you in the next day or so after I spend some more time tracking this down.

Thanks,

Joe