Guillaume Hivert

Hey! Actually your message made me think more, and I released an update for everyone. I'm still planning to do some maintenance on the project, but at least it's now...

Thanks to confirm it works!

Hi! Thanks for opening the subject! I'm planning to rewrite an enhanced version of Tardis, so it will be taken into account! 😉

I can confirm that behaviour [is enforced here in `pg_types` here](https://github.com/tsloughter/pg_types/blob/6185ed2e015b573c3decaee5caffd6c719495e14/src/pg_timestamp.erl#L85). `decode_timestamp0` add micro-seconds if there's any (which will probably happen when using `current_timestamp` in SQL).

> Oh! Should that last one be a float then? I presume people would want to lose that level of precision. That is my opinion too. Plus, to make it...

Wow, time ran out, and I forgot to answer. What I meant is that by default, I suppose we could truncate to seconds, and simply not take into account milliseconds...

Do not worry, while you can make a constructive argument about a solution or another, and it's not off-topic. I think it's nice to have different opinions on the subject!...

Sorry for taking so long time to take action. Finally I suggest to use the correct format output by `pgo`, and to not keep precision. Users will always be able...

Implemented as `Timestamp` in newer release. Thanks!

Hi everyone! @lpil told me about a potential rewrite with Lustre in Gleam. I’d be happy to help on the subject and implement the frontend part! If I understand everything...