Hello,

I have a piece of code that inserts a row in a table and then some time later in the code that same row is fetched, but all within the same transaction.

In between those two events, the inserted row is saved to persistent storage but not commited.

Now, I've been using a transaction with isolation level set to ReadCommited, and when the saved row was about to be fetched, LLBL hanged, which was understandable.

But, when I changed the isolation level to ReadUncommited, the same thing is happening. LLBL still hangs when trying to read inserted row.

My understanding is that there are no locks when isolation level is set to ReadUncommited. Why is this happening? Is there a way to read a previously inserted row which is saved in the mean time but not commited?

Thanks!

Using latest build of LLBLGen Pro 2.6, C#, SQL Server 2005 Enterprise, and two classes self servicing scenario.

Take a look at this: http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=10512

Thanks!

I solved it on my own by adding entity that reads the value from the database to the transaction.