Jeremy Morton <ad...@game-point.net> writes:
> At just about every development shop I've worked for, I've seen
> developers use methods to get a local DateTime - both in the DB and in
> the code - such as DateTime.Now, and throw it at a DateTime field.
> Heck, even I've occasionally forgotten to use .UtcNow. With
> DateTimeOffset.Now, you can't go wrong. You get the UTC time, and the
> offset. I've taken to using it 100% of the time. It's just really handy.
It sounds like what you are describing is a client-side problem, not
a server issue. If you have such a thing in the client code, why
can't it readily be mapped to timestamptz storage in the server?
regards, tom lane
