- ///
+ ///
/// The value stored in the database depends on what your data provider is capable
- /// of storing. So there is a possibility that the DateTime you save will not be
- /// the same DateTime you get back when you check DateTime.Equals(DateTime) because
+ /// of storing. So there is a possibility that the DateTime you save will not be
+ /// the same DateTime you get back when you check because
/// they will have their milliseconds off.
- ///
- ///
- /// For example - SQL Server 2000 is only accurate to 3.33 milliseconds. So if
+ ///
+ ///
+ /// For example - SQL Server 2000 is only accurate to 3.33 milliseconds. So if
/// NHibernate writes a value of 01/01/98 23:59:59.995 to the Prepared Command, MsSql
/// will store it as 1998-01-01 23:59:59.997.
- ///
- ///
+ ///
+ ///
/// Please review the documentation of your Database server.
- ///
+ ///
+ ///
+ /// If you are looking for the most accurate date and time storage accross databases use the
+ /// .
+ ///
///
+ [Obsolete("Please use DateTimeType instead.")]
[Serializable]
- public partial class TimestampType : PrimitiveType, IVersionType, ILiteralType
+ public class TimestampType : AbstractDateTimeType
{
- ///