Hello together...

I got a problem with hibernate and flushing objects. For example, I create a number of new objects and use the "Save" method of the current Session to indicate to hibernate, that those are new instances. When I'm done with my loop, I use a flush() to write the data to the database. However, only the last created object becomes persistent.

The same happens, if I first delete an object from the database (using delete on the session) and then re-create the object. When I do a flush then, I get a key violation, because the object was never deleted. Shouldn't the flush remember that I wanted to delete the object and do that first, prior to do the insert?

Does anyone have an idea how to fix this behaviour? It's kinda pointless if I have to do a flush after every command.

Kind regards, Marco...

Just a tought: have you tried to open a transaction before entering the loop?
Can you post the code, please?

Cheers,
Radu

Hi Radu,

no, I'm not using an transaction. Here is the code I use:

[TestFixtureSetUp]
public void Init()
{
m_UserProvider = PlatformProvider.Get.User;
Finalize();
ISession DBSession = SCPApp.GetDBSession();
try
{

for (int i = 0; i < 50; i++)
{
m_UserProvider.CreateNewUser("unittest" + i.ToString("D2"), "password" + i.ToString(), DBSession);
}
}
finally
{
DBSession.Flush();
DBSession.Close();
}
}

It works, if I do the flush directly after the CreateNewUser. Here is also the code for "CreateNewUser":

public IUser CreateNewUser(string LoginName, string Password, ISession DBSession )
{
IUser Result = new User();

Result.LoginName = LoginName;
Result.Password = Password;
Result.ACL.OwnerID = Result.ObjectID;
AssignDBSession(Result, DBSession);
Result.Save();
return Result;
}

Regards, Marco...

are you sure that your 50 objects have 50 different id?

radu

Hi Radu,

yes, I'm sure. I use a Guid as ID and assign it during the save process myself (though I guess it get's overwritten by the comb ID generator later on).

Regards, Marco...

well, just to check the behaviour, enclose the loop in a transaction. In fact Hibernate best practices require to always use a transaction. Usually a simple save involves more than one sql statements.

Radu

Ok, I tried putting the whole thing into a transaction and commit it in the end. No difference. I can even see NHibernate "saving" the objects, including the object id. But the flush (triggered through the commit) does only save the last entry (unittest49). Any other ideas?

Kind regards, Marco

post the full code and mapping file

radu