search

mbucc / shmig

Database migration tool written in BASH.
BSD 3-Clause "New" or "Revised" License
461 stars 50 forks source link

Consider using a date instead of unix timestamp #32

Closed asabil closed 5 years ago

asabil commented 7 years ago

A timestamp in the form of YYYYMMDDHHMMSS is generally easier to relate to than unix timestamps.

mbucc commented 6 years ago

I usually only care about the ordering and the time stamp is added to the file itself.

Also, epoch seconds include timezone (they are always in GMT) which is a win.

Thanks for your input, but I'm going to close this.

kael-shipman commented 6 years ago

Hey all,

As the author of a similar issue, #42, I just wanted to add my two cents to this.

In my opinion, the point of implementing this as a config item is so we can both have our way. If we can figure out the ordering issues that I ran into implementing this in the database (which to me are fairly minor), then adding this feature really won't affect you at all :).

Sure, we don't just want to implement any old feature that gets suggested, but this seems like one of those personality things where half the people are going to want to do it one way and the other half are going to want to do it the other way, and it's easy to give them both their way.

I've already started implemented this (see my human-timestamps branch), so it would be great if we could figure out how to get it into master so everyone can be happy :D.

mbucc commented 6 years ago

Reopening.

mbucc commented 5 years ago

I'm going to pass on this. I think there are already too many options. I also don't want to get into timezone, timezone format, offset, Z, nothing complexity.