MsSQL2005 server has 3millisecond precision issue. The issue was solved in MsSQL2008 with DATETIME2.
2009/7/15 Graham Bunce <[email protected]> > > All, > > I'm going to try to create a failing test for this but before I do, is > it a known issue? > > I'm creating a new object with a datetime mapped to a timestamp column > property (e.g. "Last Read Timestamp"). This datetime is set to (e.g. > 2009-10-09 12:43:11.222). > > I add the entity to the session and then flush it (before I allow the > code to flush I check the content of the property in debugger and its > as I expect. When I check the SQL profiler (SQL Server 2008) I notice > the parameter is not set to "2009-10-09 12:43:11.222" but in fact > "2009-10-09 12:43:11.223"... i.e. the millisecond has changed. > > Looks like some kind of conversion/rounding error but I can't think > why. > > I'm using the SQL Server 2005 dialect. Mapping is: > > <property name="DateTime" column="MovementDateTime" > type="Timestamp" not-null="true" /> > > SQL column is: [MovementDateTime] [datetime] NOT NULL, > C# is: private DateTime _dateTime; > > Thanks > > > -- Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
