You can create an object, set Id, and other properties on your own, and save it without worrying about the Hibernate Session exception.

If you’re using save Or Update, the object saved MUST be attached to session. This means you can create a copy of object from Service layer and just pass the object to your DAO.

saveorupdate is not updating-90

After the contact is saved to Outlook, you can get updated information from the directory at any time, such as a new job title or office number.

Do any of the following: Save a contact from a directory Update a contact from a directory If you add a contact to Outlook, and the e-mail address matches that of a contact in one of your directories, Outlook automatically displays some directory information about that contact.

If you have a Microsoft Exchange account or a directory services account, you can save a contact from the directory to Outlook.

This allows you to add information to the contact, such as a mobile phone number, that is not available in the directory.

In my previous and current project, I have run into cases where I needed to save an object to database using hibernate, and from time to time, I run into some sort of Hibernate Session Exception.

I did a bit of google search, and it turns out that when saving an object, I needed to make sure the object was attached to Hibernate session.

How does NHibernate handle this type of database transaction? But to be clear, you won't use a second session in your production environment.

When you are used to keeping track of your objects manually and updating them when needed you don't tend to think of this dirty tracking idea as anything special. (unless you want to) You can still tell NHibernate to save the object, it's just not needed in the event of an update.

/// public virtual T Save Or Update And Refresh(T entity) As you can see, this method calls Save Or Update followed by a Flush and Refresh prior to returning the object.

To test this out, I created a simple domain object.

The first time I profiled an application using NHibernate Profiler and performed a save without any changes, I was shocked because NHibernate didn't write the TSQL to update the database. Once this transaction is committed, NHibernate will write the TSQL to delete this object from the database. Edit(1) Dim Get Model As User = Direct Cast(Get Result. I thought originally that you could just create a new object with an id of zero, tell NHibernate (in the configuration) that zero = new object and it would insert automatically. Create(Nothing) 'now pull the user back out and verify the address was updated Dim Get Controller As User Controller = New User Controller() Dim Get Result As View Result = Get Controller.