Programming

23332 readers

329 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 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

UlrikHD@programming.dev

Excel vs database (sh.itjust.works)

submitted 4 days ago by bridgeenjoyer@sh.itjust.works to c/programming@programming.dev

11 comments fedilink hide all child comments

I always see the programmer sentiment that "people should not be using excel for (project). It should be a database."

I am guessing by that they mean SQL? I dont know a thing about that except the acronym. The most ive done is a basic linux script and 2 hours of a VBA course. I suck at understanding programming, so id like to understand exactly how one uses a database vs excel. Like whay are the actual steps id have to do?

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

[–] capuccino@lemmy.world 16 points 3 days ago* (last edited 3 days ago)

The most simple way to understand this is that databases are made to be proof to failures. When you write a single value into the database a lot of things are happening behind to ensure something called ACID, by other hand, excel documents are a monolith file, doesn't have a mecanism behind to rely and ensure the integrity of the data.

Edit: changed the link to ACID.