I don't know about Oracle, sorry, but there was a similar bug I raised recently with the SQL Server 2008 dialect DATETIME2. It seemed the dialect wasn't generating the milliseconds properly as it hadn't overridden the base class correctly. SQL did generate milliseconds as I would expect for Timestamp mapped columns.
Maybe there is a similar bug in the Oracle dialect? If you can, I suggest writing a test case to prove the problem then raise it as JIRA bug - I think 2.1.1 is near completion, maybe it can be slipped in if it is a bug --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
