/OskarI'm looking into it.My take is that if we're using (modern) MSSQL over ODBC we should set dbParam.Scale = 3 if the DbType is DateTime and nothing else have bee specifiedFor the lack of real bug reports showing issues on other environments, I'm consider doing a somewhat hacky solution. It seems like it's more about how the tests are written and executed, than a bug in NHibernate itself. But we don't really want to change a massive amount of tests because then maybe they wouldn't test what they were supposed to test anymore. Besides all the work required.2016-07-28 17:38 GMT+01:00 'Nathan Brown' via nhusers <nhu...@googlegroups.com>:A large number of unit tests are failing because of the following error:--System.Data.Odbc.OdbcException : ERROR [22008] [Microsoft][SQL Server Native Client 11.0]Datetime field overflow. Fractional second precision exceeds the scale specified in the parameter binding.What is the approach the team wants to take to resolve this? Should the NHibernate SQL Server mappings automatically truncate these datetime fields? Should the unit tests truncate? Should the schema be updated to use datetime2 so it can handle the full precision?Any other options available?Above all, I think the unit tests should have a path to passing on all servers, especially MS SQL Server.Thanks,Nathan Brown
You received this message because you are subscribed to the Google Groups "nhusers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nhusers+u...@googlegroups.com.
To post to this group, send email to nhu...@googlegroups.com.
Visit this group at https://groups.google.com/group/nhusers.
For more options, visit https://groups.google.com/d/optout.