odp.net mixes up / caches clob column

I have an ASP.NET 4.0 application where I'm using NHibernate 3.0 with ODP.NET (newest version) to access a Oracle Express 10g database. All is working fine except the CLOB column is getting mixed up in my objects.

Example:

Http request /product/1/:

All returned columns values are OK.

Http request /product/2/:

All returned columns values are OK, except the CLOB column. The returned CLOB column is from the previous loaded object.

The problem disappears when disabling connection pooling.

But I'd like to use connec开发者_如何学Pythontion pooling and it doesn't feels right as a solution. Is this a bug in the ODP.NET or are I'm missing some built-in "feature"?

---

I had a similar problem and setting "Statement Cache Purge=true" in the connectionstring solved it. But I admit it's a very strange case because it occurs only with clob.

---

May you could try to set the metadata pooling attribute to false, when declaring ODP's connection string. See doc: Supported Connection String Attributes