Programming

17374 readers

253 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

119

You might as well timestamp it (changelog.com)

submitted 1 year ago by jerodsanto@programming.dev to c/programming@programming.dev

21 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] alertsleeper@programming.dev 6 points 1 year ago (1 children)

I think this timestamp-as-a-boolean is a good idea if the field is always going to be interpreted as either True or False and nothing more. If the field in question allows for a 3rd (uncertain) value, then using a timestamp would be extremely confusing.

[–] canpolat@programming.dev 3 points 1 year ago

And it all depends on the problem at hand. Any of those solutions can be acceptable as long as you have a well thought out model.