Programming

17308 readers

217 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 [email protected]

founded 1 year ago

MODERATORS

snowe

Ategon

[email protected]

121

You might as well timestamp it (changelog.com)

submitted 1 year ago by jerodsanto to c/programming

18 comments fedilink hide all child comments

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

[–] learningduck 3 points 1 year ago (1 children)

How do you update it to unoublish? Add another timestamp column and who's the latest win or just set published_at to null?

[–] pie 2 points 1 year ago (1 children)

You wouldn't store this information on the same table (unless you're using a wide row db like dynamo/Cassandra). In a SQL world, you'd store version information in a separate table - one table for the HEAD state and another for history.

[–] learningduck 1 points 1 year ago

So, the history table have every column, but the user table has only user id and version, right?

user_history table user table