When implemented by a class, puts the value/values from the mapped
class into the IDbCommand.
Namespace: NHibernate.TypeAssembly: NHibernate (in NHibernate.dll) Version: 3.2.0.4000 (3.2.0.4000)
Syntax
C# |
---|
public override sealed void NullSafeSet( IDbCommand st, Object value, int index, ISessionImplementor session ) |
Visual Basic |
---|
Public Overrides NotOverridable Sub NullSafeSet ( _ st As IDbCommand, _ value As Object, _ index As Integer, _ session As ISessionImplementor _ ) |
Visual C++ |
---|
public: virtual void NullSafeSet( IDbCommand^ st, Object^ value, int index, ISessionImplementor^ session ) override sealed |
Parameters
- st
- Type: System.Data..::..IDbCommand
The IDbCommand to put the values into.
- value
- Type: System..::..Object
The object that contains the values.
- index
- Type: System..::..Int32
The index of the IDbDataParameter to start writing the values to.
- session
- Type: NHibernate.Engine..::..ISessionImplementor
[Missing <param name="session"/> documentation for "M:NHibernate.Type.NullableType.NullSafeSet(System.Data.IDbCommand,System.Object,System.Int32,NHibernate.Engine.ISessionImplementor)"]
Implements
IType..::..NullSafeSet(IDbCommand, Object, Int32, ISessionImplementor)Remarks
Implementors should handle possibility of null values.
A multi-column type should be written to parameters starting from index.
Remarks
This implementation forwards the call to NullSafeSet(IDbCommand, Object, Int32).
It has been "sealed" because the Types inheriting from NullableType do not need to and should not override this method. All of their implementation should be in NullSafeSet(IDbCommand, Object, Int32).