Is it supported to materialize a LOB locator outside the transaction in which it was created?

Again, part of the trickiness here is the fact that this is largely driver dependent.

NOTE: all database I have tested which {@link #supportsExpectedLobUsagePattern()} also support the ability to materialize a LOB outside the owning transaction...

public virtual bool SupportsUnboundedLobLocatorMaterialization { get; }

Public Overridable ReadOnly Property SupportsUnboundedLobLocatorMaterialization As Boolean
	Get

public:
virtual property bool SupportsUnboundedLobLocatorMaterialization {
	bool get ();
}