A loooooong time ago I created the following issue regarding the fact that
the Timestamp type does not use DateTime.UtcNow
https://nhibernate.jira.com/browse/NH-2520
The Timestamp behavior (not using UTC) by itself is already a bug IMHO but
I get it to not change the behavior for backwards compatibility. For this
reason I create the supplied patches to the ticket that supply a new type
TimestampUtc
For some reason this is never merged as I don't see it on github:
https://github.com/nhibernate/nhibernate-core/tree/master/src/NHibernate/Type
However, the current behavior has bitten me again as it is so strange that
it does not by default use DateTime.UtcNow this time I work at a new
project at a new company.
Optimizations and improvements:
* Utc values are a must for global replicated databases/systems
* DateTime.UtcNow is *MUCH* faster then DateTime.Now
When I create a new version based on the current master and create a pull
request for this type will it then be included?
-- Ramon
--
---
You received this message because you are subscribed to the Google Groups
"nhibernate-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
