upvote

points

by alexpotato11 hours ago |
comments
upvoteby Fwirt10 hours ago|
next
[-]
The question is, do the same firms ban Excel? Excel spreadsheets often end up as shadow databases in unlikely places.
reply
upvoteby croon3 hours ago|
parent|
next
[-]
This might catch flak, but generalizing I would assume that the people banning things are the same people who would use excel for something where a database would be better, and if so, that is the reason Excel isn't banned on the same conditionals that would get sqlite banned.
reply
upvoteby hermitShell10 hours ago|
parent|
prev|
next
[-]
The sane thing would be to ban Excel and promote SQLite. Excel is often used for tabulated text (issue tracking) not calculations. Perfect use case for a relational db
reply
upvoteby frollogaston10 hours ago|
parent|
next
[-]
Excel is made for calculations. But if you make it hard to make a DB, people will abuse Excel as a DB.
reply
upvoteby TJSomething7 hours ago|
parent|
[-]
I mean, it might have been at first, but Microsoft figured out that the majority of users for lists without formulas in 1993 and they've strategized around that. IMHO, the biggest concession to this was when they added Power Query to core Excel in 2016.
reply
upvoteby rswail5 hours ago|
parent|
prev|
next
[-]
Excel has sheets for tables, columns and rows, primary keys (UNIQUE), foreign key references etc if you squint.

It doesn't require you use all of that properly, but it's there.

reply
upvoteby harvie4 hours ago|
parent|
prev|
next
[-]
or reimplement excel with sqlite as a backend :-D

BTW sqlite can run SQL queries on CSV files with relatively simple one-liner command...

reply
upvoteby 0123456789ABCDE5 hours ago|
parent|
prev|
[-]
and excel has gui for forms
reply
upvoteby rantingdemon4 hours ago|
parent|
[-]
Only where VBA is available. Not available for MacOs versions if I'm correct?
reply
upvoteby nereye14 minutes ago|
parent|
[-]
VBA is just there for backward compatibility.

The modern alternative is to use JavaScript/TypeScript, which makes such solutions cross platform (including MacOs, web etc.):

https://learn.microsoft.com/en-us/office/dev/add-ins/overvie...

reply
upvoteby mr_toad2 hours ago|
parent|
prev|
next
[-]
I’ve worked at some organisations that have strict rules (not always strictly followed) about what can go in Excel spreadsheets, and where they have to be stored. The C drive is verboten. Some also have standards about classification and labelling of PII and sensitive data.
reply
upvoteby silon427 hours ago|
parent|
prev|
next
[-]
IMO, almost any Excel more than a month old should become readonly.
reply
upvoteby irishcoffee2 hours ago|
parent|
[-]
You should consider knock-on effects of this brilliant idea. Now there would be copies of spreadsheets younger than a month that get replicated 47 billion times, exponentially compounding the problem you're trying to solve.

This sounds like how we pass so many stupid laws. Nobody thinks about 2nd order effects.

reply
upvoteby perching_aix1 hours ago|
parent|
[-]
So you're saying they should further auto-delete after two or three months?
reply
upvoteby irishcoffee1 hours ago|
parent|
[-]
3rd order effect, people copy and paste the old sheet into a new sheet, now we have worse exponential. You’re not very good at this huh.
reply
upvoteby perching_aix1 hours ago|
parent|
[-]
Which is very annoying and people will complain. People complaining can be then directed towards a better solution. As a bonus, mistakes will also rise, leading to further complaints, especially ones that reach higher. All this making the dogshit practice, and the idiots committing them, infinitely more visible and thus fixable.

The sheer volume of data that needs tending to may even grind certain departments to a halt! What a great opportunity! It'd appear I'm positively stellar at this!

reply
upvoteby Spooky2310 hours ago|
parent|
prev|
next
[-]
They generally cannot. But they do banish Access.
reply
upvoteby pasc18786 hours ago|
parent|
[-]
Now that is different.

Access gets used for a shared DB and that is quite easy to corrupt. It is much more cost effective to have that in a proper central database (I supse SQLLite is better here as well)

reply
upvoteby cwillu3 hours ago|
parent|
[-]
Excel is also a shared DB: it has supported multiple concurrent users accessing and modifying the same spreadsheet for decades.
reply
upvoteby 8 hours ago|
parent|
prev|
next
[-]
deleted
reply
upvoteby DeathArrow8 hours ago|
parent|
prev|
[-]
Do companies ban text files? Text files are used to store data.
reply
upvoteby perching_aix1 hours ago|
parent|
next
[-]
That's why you store them in unsaved tabs instead.
reply
upvoteby yard20105 hours ago|
parent|
prev|
next
[-]
Do companies ban data centers? It's crazy to send PII to other computers on the line.
reply
upvoteby altmanaltman5 hours ago|
parent|
prev|
[-]
Do companies ban brains? Brains are used to store data.
reply
upvoteby Scribbd47 minutes ago|
prev|
next
[-]
I recently watched a YT video about this subject: https://www.youtube.com/watch?v=lSVgeMoXJTs

In summary, companies use the bus-metric to see how viable a project is. Bus, as in, how many people can be hit by a bus before there is no one left to maintain the project.

Despite its ubiquity, SQLite is maintained by only 3 people. That bus-metric for SQLite is 3, which is way too low for some companies.

Give the link a watch; it was really interesting.

reply
upvoteby BenjiWiebe28 minutes ago|
parent|
[-]
At least with SQLite, it is really stable so if development did cease, you'd probably be fine indefinitely.
reply
upvoteby tehlike9 hours ago|
prev|
next
[-]
There are interesting uses for sqlite, like this one: https://sqlite.org/sqlar.html
reply
upvoteby gandutraveler2 hours ago|
prev|
next
[-]
DevOPs and DBAs must hate RAM and caches. We
reply
upvoteby ai_slop_hater11 hours ago|
prev|
next
[-]
That's so dumb
reply
upvoteby slopinthebag10 hours ago|
prev|
[-]
> DevOps and DBA teams

Ah so two teams nobody should listen to.

reply
upvoteby frollogaston10 hours ago|
parent|
[-]
At least would take it with a grain of salt when the DBA wants you to depend more on the DBA.
reply
upvoteby slopinthebag10 hours ago|
parent|
[-]
Same with devops tbh.

"Hey everyone, we need to chose the option that involves us the most and provides us the most job security"

reply
upvoteby mschuster915 hours ago|
parent|
[-]
Well... eventually the company learns the lesson the hard way, either because a site goes down or gets 0wned. Then everyone will cry about "how this could happen", and the ops people will tell you in response "we warned you that this would happen, here's the receipts, now GTFO".
reply