Does the dialect support propagating changes to LOB values back to the database? Talking about mutating the internal value of the locator as opposed to supplying a new locator instance...

For BLOBs, the internal value might be changed by: {@link java.sql.Blob#setBinaryStream}, {@link java.sql.Blob#setBytes(long, byte[])}, {@link java.sql.Blob#setBytes(long, byte[], int, int)}, or {@link java.sql.Blob#truncate(long)}.

For CLOBs, the internal value might be changed by: {@link java.sql.Clob#setAsciiStream(long)}, {@link java.sql.Clob#setCharacterStream(long)}, {@link java.sql.Clob#setString(long, String)}, {@link java.sql.Clob#setString(long, String, int, int)}, or {@link java.sql.Clob#truncate(long)}.

NOTE : I do not know the correct answer currently for databases which (1) are not part of the cruise control process or (2) do not {@link #supportsExpectedLobUsagePattern}.

public virtual bool SupportsLobValueChangePropogation { get; }

Public Overridable ReadOnly Property SupportsLobValueChangePropogation As Boolean
	Get

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