Definitely use local-time. The integration worked well, back in 2007, and neither library has changed very much since then, so I think you can feel safe that they are in good shape (others are using them as well). On Mon, Dec 30, 2013 at 3:55 PM, Eli Naeher <enaeher@gmail.com> wrote:

Hello,

I'm working on moving an existing application to Postmodern, and I'm trying to decide whether to go with simple-date or local-time. Currently all dates are stored as "timestamp without time zone," but we are hoping to move toward a timezone-aware model at some point down the road (although not immediately--it might end up being a couple years).

For this reason I'm considering using local-time instead of simple-date. Times and dates are a big part of the application so I'd like to get this right. I notice that the local-time cl-postgres integration has not had any commits in a few years. I'm hoping this is because it is stable and complete. Is anyone using it?

Thank you, -Eli

are stored as "timestamp without time zone," but we are hoping to move toward a timezone-aware model at some point down the road (although not immediately--it might end up being a couple years).

just a quick note that local-time timestamps are also not aware of timezones either, and that is fine that way. only the conversion functions are aware of timezones, e.g. when printing a timestamp into a calendar system defined string of characters that humans can understand, or when e.g. creating a timestamp from user input. also note that local-time has quite some TODO's documented in its TODO file. but other than that it works. https://github.com/dlowe-net/local-time/blob/master/TODO.org -- • attila lendvai • PGP: 963F 5D5F 45C7 DFCD 0A39 -- “People focus on role models; it is more effective to find antimodels - people you don't want to resemble when you grow up.” — Nassim Taleb (1960–)