Why would you need a full blown (shitty) relational database management system to store gene info? Excel should be just fine for storing data in arbitrary tables. It shouldn’t make assumptions about your data by default, and changing values that look like they’re in a specific format should be opt-in, not default behavior.
It shouldn’t make assumptions about your data by default, and changing values that look like they’re in a specific format should be opt-in, not default behavior
But that’s exactly what made the “auto” data type of Excel such a powerful tool when introduced. If you’re storing text, make the datatype “text”, problem solved.
Nowadays, when making stuff like Excel from scratch, you could opt for a “these look like dates, change the type from ‘none’ to ‘date’?” but with middle management being conditioned on the data type being ‘auto’, that’s something that’s hard to change.
Honestly, I’d say you shouldn’t do that prompt method. The auto type is genuinely great for the use cases which Excel is supposed to be used for, from someone managing their household finances to charting the growth of a business.
By all means, it absolutely should make assumptions about your data by default, as that’s incredibly convenient for the average user. You can always change the type of a cell afterwards if what you’re doing is special.
That is not what it was made for. It was made to do shenanigans with values like doing math on them and plotting graphs. If you merely want data storage, use a table. I agree, a database is overkill for most things, but that doesn’t change the fact that Excel is the wrong tool for the job. Maybe if they added a table mode where it’s basically just a frontend for a csv it’d work, but right now I’d still say it’s better to use a scalpel than a hammer, even if scissors do the trick just fine.
Why would you need a full blown (shitty) relational database management system to store gene info? Excel should be just fine for storing data in arbitrary tables. It shouldn’t make assumptions about your data by default, and changing values that look like they’re in a specific format should be opt-in, not default behavior.
But that’s exactly what made the “auto” data type of Excel such a powerful tool when introduced. If you’re storing text, make the datatype “text”, problem solved.
Nowadays, when making stuff like Excel from scratch, you could opt for a “these look like dates, change the type from ‘none’ to ‘date’?” but with middle management being conditioned on the data type being ‘auto’, that’s something that’s hard to change.
Optimist: The glass is half full.
Pessimist: The glass is half empty.
Realist: The glass is twice as big as necessary.
Excel: The glass is the 2nd of January.
Honestly, I’d say you shouldn’t do that prompt method. The auto type is genuinely great for the use cases which Excel is supposed to be used for, from someone managing their household finances to charting the growth of a business.
By all means, it absolutely should make assumptions about your data by default, as that’s incredibly convenient for the average user. You can always change the type of a cell afterwards if what you’re doing is special.
That is not what it was made for. It was made to do shenanigans with values like doing math on them and plotting graphs. If you merely want data storage, use a table. I agree, a database is overkill for most things, but that doesn’t change the fact that Excel is the wrong tool for the job. Maybe if they added a table mode where it’s basically just a frontend for a csv it’d work, but right now I’d still say it’s better to use a scalpel than a hammer, even if scissors do the trick just fine.
Agree. Excel is terribly inefficient if your goal is just storing data.
Sqlite and duckdb are great, I don’t know about shitty.
You don’t get the visual feedback but the query language, reliability and python interface are all top notch.